Lighting system for medical appointment progress tracking by wireless detection

ABSTRACT

Provided are mechanisms and processes for a lighting system for medical schedule management. According to various examples, an apparatus is provided which comprises a lighting interface configured to connect to a lighting element for illuminating a medical examination room. The apparatus further comprises a power interface coupled to a power source. The apparatus further comprises a Wi-Fi transceiver configured to transmit a wireless signal to connect to a device corresponding to a physician. The wireless signal corresponds to a local area network. The duration of the connection is used to track the presence of the physician in the medical examination room. The Wi-Fi transceiver is tuned to transmit a signal strength corresponding to the size and characteristics of the medical examination room. The apparatus is located in a lighting fixture in the medical examination room. The lighting fixture may be centrally located in the medical examination room.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/439,792 entitled: “LIGHTING SYSTEM FOR MEDICAL APPOINTMENT PROGRESSTRACKING BY WI-FI DETECTION” filed on Feb. 22, 2017, which isincorporated herein by reference in its entirety for all purposes.

BACKGROUND

Medical appointments are commonly associated with notoriously long waittimes. According to numerous reviews from patients, the number onecomplaint is the wait time to see the doctor. For instance, onlinereview sites allow patients to comment and provide corresponding starratings for service providers. On these sites, low star ratings forphysicians are often associated with comments citing long wait times.Often, reviewers complain of waiting from between thirty minutes to twohours. These reviews indicate that patient satisfaction with aphysician's care can be heavily influenced by wait times, and thatexcessive wait times can lead to negative reviews of a physician'sservices.

Accordingly, improving the wait time for a patient can greatly improvethe patient's satisfaction with the physician. In turn, thissatisfaction will improve the patient's subjective feelings about theircare, which can lead to more effective treatment and service.Specifically, when the patient is in a positive frame of mind at thebeginning of the examination, the appointment naturally flows moresmoothly. In addition, physicians often note that when they are behindschedule, they often spend time apologizing to the patient about beinglate, which reduces the amount of time available for actual patientcare. By reducing or eliminating patient wait times, physicians can bemore efficient and patients can have more positive experiences atappointments. Consequently, there is a need for improving patient waittimes for medical appointments.

SUMMARY

Provided are various mechanisms and processes relating to an appointmentscheduling management system. Although medical scheduling is used as amain example, those of ordinary skill in the art will recognize that thesame problems may exist in any appointment-based service practice(including but not limited to dental, veterinary, legal, accounting,counseling, cosmetology, photography or auto repair concerns) and mayaccordingly be addressed by the subject matter of this disclosure.

In one aspect, which may include at least a portion of the subjectmatter of any of the preceding and/or following examples and aspects, anapparatus is provided which comprises a lighting interface configured toconnect to a lighting element for illuminating a medical examinationroom. The apparatus further comprises a power interface coupled to apower source. The apparatus further comprises a Wi-Fi transceiverconfigured to transmit a wireless signal to connect to a devicecorresponding to a physician. The duration of the connection is used totrack the presence of the physician in the medical examination room. Thetransceiver is tuned to transmit a signal strength corresponding to thesize and characteristics of the medical examination room. The apparatusis located in a lighting fixture in the medical examination room. Thelighting fixture may be centrally located in the medical examinationroom.

The Wi-Fi transceiver may be configured to transmit a plurality ofmulticast data packets to the device during the duration of theconnection. Each multicast data packet may include informationidentifying the medical examination room. The Wi-Fi transceiver may beconfigured to receive a plurality of multicast data packets from thedevice during the duration of the connection. Each multicast data packetmay include information identifying the corresponding physician.

The apparatus may be configured to log a timestamp based on the detectedsignal indicating the beginning of a first appointment. The apparatusmay further be configured to compare the timestamp with schedulinginformation to predict whether future appointments will be delayed.Scheduling information may include a plurality of scheduled appointmentswhich include the first appointment and a second appointment.Determining whether the second appointment will be substantially delayedincludes comparing a second time associated with the second appointmentwith an originally scheduled time for the second appointment. The secondtime may be predicted based on an amount of delay from the firstappointment. The apparatus may be further configured to notify a holderof the second appointment if the second appointment is determined to besubstantially delayed.

In some embodiments, Wi-Fi transceiver may comprise a plurality ofwireless routers. A first router may be configured to receive a wirelessnetwork signal corresponding to the network signal of the local areanetwork. A second router may be configured to rebroadcast the wirelessnetwork signal as the wireless signal.

In other embodiments, the Wi-Fi transceiver may comprise a powerlineadapter coupled to the power source via an electrical circuit. Thepowerline adapter may be configured to receive the network signal of thelocal area network over the electrical circuit and transmit the networksignal as the wireless signal. The Wi-Fi transceiver and the lightingelement may be electrically coupled in parallel.

Other implementations of this disclosure include corresponding methods,devices, systems, and computer programs, configured to perform theactions of the described method. For instance, a system is providedcomprising a lighting fixture in a medical examination room, and alocation tracker in the lighting fixture. The location tracker comprisesa lighting interface configured to connect to a lighting element forilluminating the medical examination room. The location tracker furthercomprises a power interface coupled to a power source. The locationtracker further comprises a Wi-Fi transceiver configured to transmit awireless signal to connect to a device corresponding to a physician. Thewireless signal may correspond to a local area network. The duration ofthe connection is used to track the presence of the physician in themedical examination room. The Wi-Fi transceiver is tuned to transmit asignal strength corresponding to the size and characteristics of themedical examination room. The lighting fixture may be centrally locatedin the medical examination room.

In another aspect, which may include at least a portion of the subjectmatter of any of the preceding and/or following examples and aspects, amethod for appointment progress tracking is provided. The methodcomprises coupling a power interface of a lighting system to a powersource. The lighting system may comprise a lighting fixture in a medicalexamination room. The lighting fixture may include a lighting interfaceconfigured to connect to a lighting element for illuminating the medicalexamination room. The lighting fixture may further include a Wi-Fitransceiver configured to receive a network signal of a local areanetwork. The lighting fixture may be centrally located in the medicalexamination room.

The method further comprises transmitting, via the Wi-Fi transceiver, awireless signal to connect to a device corresponding to a physician. Thewireless signal corresponds to the network signal. The method furthercomprises tuning the signal strength of the wireless signal tocorrespond to the size and characteristics of the medical examinationroom.

In some embodiments, the Wi-Fi transceiver may comprise a plurality ofwireless routers. A first router may be configured to receive a wirelessnetwork signal corresponding to the network signal of the local areanetwork. A second router may be configured to rebroadcast the wirelessnetwork signal as the wireless signal. In some embodiments, the Wi-Fitransceiver may comprise a powerline adapter coupled to the power sourcevia an electrical circuit. The powerline adapter may be configured toreceive the network signal of the local area network over the electricalcircuit and transmit the network signal as the wireless signal. TheWi-Fi transceiver and the lighting element are electrically coupled inparallel.

The method further comprises tracking the presence of the physician inthe medical examination room based on the duration of the connection. Insome embodiments, the method further comprises transmitting, via theWi-Fi transceiver, a plurality of multicast data packets to the deviceduring the duration of the connection. Each multicast data packet mayinclude information identifying the medical examination room. In furtherembodiments, the method further comprises receiving a plurality ofmulticast data packets from the device during the duration of theconnection. Each multicast data packet may include informationidentifying the corresponding physician.

The method further comprises logging a timestamp based on the durationof the connection indicating the duration of a first appointment. Thetimestamp may be compared with scheduling information to predict whetherfuture appointments will be substantially delayed. Schedulinginformation may include a plurality of scheduled appointments, whichinclude the first appointment and a second appointment. The method mayfurther comprise notifying a holder of the second appointment if thesecond appointment is determined to be substantially delayed.

These and other embodiments are described further below with referenceto the figures.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow chart illustrating one example of a patient appointmentsequence.

FIGS. 2A-2E are diagrams illustrating one example of a system ofsensors, identifiers, and their signals.

FIG. 3 is a swim-lane diagram of propagating delays of appointments.

FIGS. 4A-4C are flow sequences illustrating one example of a process forestimating delays for a medical appointment.

FIG. 5 is a swim-lane diagram of compensated delays of appointments.

FIG. 6 is a flow sequence illustrating another example of a process forestimating delays for a medical appointment.

FIGS. 7A-7C illustrate examples of user interface screens for theappointment management system.

FIG. 8 is a swim-lane diagram of multiple entries and exits of the sameindividuals to and from an examination room in the course of a singleappointment.

FIG. 9 is a flow sequence illustrating another example of a process forestimating delays for a medical appointment.

FIGS. 10A-10C are diagrams illustrating one example of a system in whichsensors are worn by patients and identifier beacons are worn byemployees and placed in service locations.

FIG. 11 is a diagrammatic representation of one example of a databasedesigned to store patient information.

FIG. 12 is a diagrammatic representation of one example of a medicalscheduling management system.

FIG. 13 is a diagrammatic representation of another example of a medicalscheduling management system.

FIG. 14 is a diagrammatic representation of an example of a lightingsystem for medical scheduling management, in accordance with one or moreembodiments.

FIG. 15 illustrates an example network architecture 1500 that can beused in conjunction with the various techniques and embodiments of thepresent disclosure.

FIG. 16 illustrates an embodiment of a typical IEEE 802.11 MAC frame1600 for a multicast data packet, in accordance with one or moreembodiments.

FIGS. 17A-17C illustrates an example method 1700 for appointmentprogress tracking, in accordance with one or more embodiments.

FIG. 18 is an example of a computer system that can be used with variousembodiments of the present disclosure.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Reference will now be made in detail to some specific examples of theinvention including the best modes contemplated by the inventors forcarrying out the invention. Examples of these specific embodiments areillustrated in the accompanying drawings. While the invention isdescribed in conjunction with these specific embodiments, it will beunderstood that it is not intended to limit the invention to thedescribed embodiments. On the contrary, it is intended to coveralternatives, modifications, and equivalents as may be included withinthe spirit and scope of the invention as defined by the appended claims.

For example, the techniques of the present invention will be describedin the context of particular scheduling mechanisms for medical offices.However, it should be noted that the techniques of the present inventionapply to a wide variety of different scheduling mechanisms for a varietyof different types of service entities such as dental offices, visionservice providers, etc., or other non-medical service entities, such asautomotive repair, dog grooming, etc. As another example, the techniquesof the present invention will be described in the context of particularwireless signals, such as Wi-Fi. However, it should be noted that thetechniques of the present invention apply to a wide variety of differentwireless signals, including Bluetooth, infrared, light of sighttransmission mechanisms, as well as various other networking protocols.

In the following description, numerous specific details are set forth inorder to provide a thorough understanding of the present invention.Particular example embodiments of the present invention may beimplemented without some or all of these specific details. In otherinstances, well known process operations have not been described indetail in order not to unnecessarily obscure the present invention.

Various techniques and mechanisms of the present invention willsometimes be described in singular form for clarity. However, it shouldbe noted that some embodiments include multiple iterations of atechnique or multiple instantiations of a mechanism unless notedotherwise. For example, a system uses a processor in a variety ofcontexts. However, it will be appreciated that a system can use multipleprocessors while remaining within the scope of the present inventionunless otherwise noted. Furthermore, the techniques and mechanisms ofthe present invention will sometimes describe a connection between twoentities. It should be noted that a connection between two entities doesnot necessarily mean a direct, unimpeded connection, as a variety ofother entities may reside between the two entities. For example, aprocessor may be connected to memory, but it will be appreciated that avariety of bridges and controllers may reside between the processor andmemory. Consequently, a connection does not necessarily mean a direct,unimpeded connection unless otherwise noted.

Medical appointments are commonly associated with notoriously long waittimes. Because patient satisfaction with a physician's care can beheavily influenced by wait times, excessive wait times can lead tonegative reviews of a physician's services. By reducing or eliminatingpatient wait times, physicians can be more efficient and patients canhave more positive experiences at medical offices. The same applies toother providers of services by appointment whose schedules may besubject to delays for various reasons.

Accordingly, various embodiments of the present invention address theissue of wait times in medical offices. In some examples, a physician'sprogress is monitored and any delays in the physician's schedule aredetected. Patients are then informed of any delays or schedule changesin real-time. Specifically, a medical scheduling management systemtracks the physician's progress and provides notifications, such asthrough text messages, to upcoming patients. These notifications can letpatients know when a physician is running behind and ask them to arrivelater than their originally scheduled appointment.

By notifying patients in real-time about schedule changes orfluctuations, the intent is to decrease the amount of time that eachpatient waits for their appointment to begin. In turn, reducing the waittime should increase patient satisfaction and result in more positiveexperiences with their physicians. Because reimbursement according toprograms like Medicare will be highly dependent on patient satisfactionin the future, the amount physicians will be paid will be closely tiedto their patients' satisfaction. By keeping patients informed ofschedule status and changes, the system described in various examples ofthis disclosure has the potential to address one of the biggest problemswith patient satisfaction: wait times. If patient satisfaction isincreased, then there is a higher likelihood that physicians will befully reimbursed for their work. In addition, higher patientsatisfaction will also lead to more referrals from patients and morebusiness for physicians.

According to various embodiments, physician and other service employeeactivities, movements, and locations can be automatically or manuallydetected to allow improved appointment scheduling. For example,appointment start times can be manually or automatically triggered whena physician enters or a room and characteristics of the appointment canbe used to determine whether later appointments need to be adjusted.

According to various embodiments, a transceiver such as a Bluetooth orWi-Fi transceiver is integrated into a lighting system centrally locatedin a medical office. In some embodiments, the transceiver is integratedinto a light bulb and is tuned to transmit at a signal strengthcorresponding to the size of the medical office. It is recognized thatusing Bluetooth or Wi-Fi is effective for roughly tracking medicalpersonnel location. However, signals leak into hallways and into otherrooms, and a Bluetooth or Wi-Fi acknowledgment signal received from amedical personnel device such as a smartphone or other location trackermay only be somewhat reliable.

Various embodiments of the present invention recognize that havingBluetooth or Wi-Fi transceivers in each medical office in a centrallylocated, easily maintained lighting fixture allows medical personnelmovement to be more easily tracked. A Bluetooth signal detected at atransceiver in a first medical office will be several times stronger ifa doctor is in the first medical office than if the doctor is in adifferent medical office. Various protocols could be used includingvarious flavors of Bluetooth, Wi-Fi, light of sight transmissionmechanisms, as well as other networking protocols. According to variousembodiments, the transceiver may operate as a Bluetooth or Wi-Fi boosteror repeater.

Furthermore, with a transceiver centrally located in an examinationroom, a wireless signal with a uniform signal strength may betransmitted to cover the examination room. However, directionality ofwireless signals may be implemented to provide fencing of such wirelesssignals by creating an aggregated signal with a signal range of aparticular shape corresponding to the room. Thus, a centrally locatedwireless transceiver may provide a more accurate indicator of when aparticular individual is within a particular room.

As such, a transceiver may be integrated into the lighting system in aroom, such as an examination room. In some embodiments, the transceiveris integrated into a light fixture. In another embodiment, thetransceiver is integrated into a light bulb. In still other embodiments,the transceiver is an adapter that attaches on one end to a conventionallighting fixture and on the other end to a conventional light bulb. Inthis way, the transceiver becomes a centrally located device with accessto continuous power. Integrating the transceiver into a lighting systemincorporates the transceiver and/or tracking system into an essentialstructure of the exam room, which may reduce clutter in an exam room inwhich limited space may already be designated for various tools,furniture, and other essential appliances. In various embodiments, thelighting element of the lighting system, such as wire filaments and/ordiodes, may function as an antenna for transmission and reception ofwireless signals.

Additionally, a transceiver may be integrated into a lighting systemwhich may be adjusted by a medical professional (such as a physician ormedical assistant) to illuminate a patient and/or a particular area ofthe patient. Thus, in various examples, the position of lighting systemmay closely correspond to the location of a patient, medicalprofessional and/or other individual or user. In this way, the proximityof an individual to lighting system may indicate when an examination hasbegun or is in progress.

Software applications may assist technicians in tuning the neededstrength of the transceivers in the light fixtures including light bulbsbased on the size and characteristics of the room. According to variousembodiments, medical personnel are not required to login, check in, ordo any extra work to indicate their presence in a room. Instead, medicalpersonnel location is tracked based on the signals received at thevarious Bluetooth or Wi-Fi transceivers.

Constraining the wireless signal to the size and characteristics of theroom may also provide additional advantages in privacy protections forsensitive private medical information protected under the federal HealthInsurance Portability and Accountability Act of 1996 (HIPAA). Forexample, the location tracking system may not be subject to unauthorizedaccess by devices not within the examination room, reducing the risk ofunauthorized access to sensitive medical information. Furthermore,unique identification codes may be used to determine location, which isfurther separated from patient appointment information, and furtherseparated from patient medical records.

In some embodiments, the transceiver may function as a Wi-Fi extender(also referred to herein as a Wi-Fi booster or repeater). A Wi-Fiextender may be configured to directly and/or wirelessly connect to anexisting network signal and rebroadcast the signal wirelessly into theroom. In some embodiments, the network signal may be transmitted to theWi-Fi extender via electrical currents in an electrical circuit. Thus,the same electrical current may provide power to the lighting system, aswell as the signal to be broadcasted. In some embodiments, the signalmay be broadcasted through lighting elements, such as wire filaments ordiodes.

Once a user device has connected with the rebroadcasted signal,information within transmitted data packets may be used to identify theroom location and/or duration of the connection. Additionally, and/oralternatively, information within data packets transmitted by aconnected user device may be used to identify the individualcorresponding to the user device and/or duration of the connection.

This disclosed system may be implemented on a secure network to furtherprovide additional advantages in privacy protections for sensitiveprivate medical information protected under HIPAA. For example, userdevices may not be authorized to connect to the secure network. However,multicast data packets may still be sent and/or received between theWi-Fi extender and user devices to indicate a connection, as well as toidentify the corresponding individual and/or room location. Suchinformation may be stored in other portions of a multicast data packet,such as the source IP address or MAC addresses. In this way, thelocation and identity of an individual, as well as the duration of theconnection, may be identified without any access to the secure networkby the user device.

In particular embodiments, mechanisms for tracking physician or othermedical personnel activities, movements, and locations for schedulingappointments are firewalled from systems managing patient medical data.In some examples, different encryption mechanisms are used to encodepatient medical data and medical personnel scheduling data so thataccess to one system does not permit access to another system. In otherexamples, different networks such as different virtual networks ordifferent physical networks are used to transport the different types ofdata. According to various embodiments, patient medical data isencrypted during both storage and transmission using a differentmechanism from medical personnel tracking data.

With reference to FIG. 1, shown is a flow chart illustrating one exampleof a patient appointment sequence. As shown, a typical patientappointment sequence 100 begins when a medical assistant (or nurse insome cases), calls a patient at 101 from the waiting room. Variousembodiments will be described with reference to particular medicalpersonnel. However, it should be noted that numerous activities can beperformed by a variety of different medical professionals such asmedical staff, medical assistants, nurses, physician assistants,physicians, residents, etc. A variety of triggers can also be used toinitiate scheduling mechanisms, such as when a physician enters thepatient's examination room, when a physician leaves the patient'sexamination room, when a nurse brings a patient to an examination room,etc.

According to various embodiments, a medical assistant then takes thepatient to the examination room at 103. During the medical assistant'ssession with the patient, the medical assistant often collectsinformation such as vitals and other data at 105. This may includeaspects such as measuring temperature, blood pressure, and the like. Inaddition, this process can include weighing and measuring the height ofthe patient. In some cases, these measurements may be taken in a hallwayon the way to the examination room. The medical assistant may also askthe patient questions and take notes. The medical assistant then leavesthe examination room and leaves the patient's chart for the physician.The patient is then left alone in the examination room to wait for thephysician. This time may also be used for changing into a gown, etc.

Next, the physician enters the examination room at 109. The physicianperforms the exam at 111, and then exits the examination room at 113.This concludes the process and the patient changes clothes, ifappropriate, and collects their belongings before leaving theexamination room.

As described, a medical appointment includes various phases that mayinclude wait times. For instance, the patient may wait for a period oftime before the medical assistant initially calls the patient at 101.The patient may also wait for a period of time between the time themedical assistant leaves the room at 107 and the time the physicianenters the room at 109. Both of these wait times affect patientsatisfaction and can lead to complaints relating to patient care. Inaddition, the amount of time that a physician spends with a particularpatient, between blocks 109 and 113, affects whether future appointmentsthat day will be on time or delayed. Accordingly, the timing of variousphases of a patient appointment sequence can affect patient satisfactionand determine whether future appointments will be delayed.

FIGS. 2A-2E are diagrams illustrating one example of a system ofsensors, identifiers, and their signals.

With reference to FIG. 2A, shown is an example of a partialmedical-office floor plan with an example of the system installed.Physician 203, shown in office 230, is the wearer of physician'sidentifier 231. Physician's identifier (ID) 231 may be an active beaconor a non-powered readable tag such as an RFID or infrared tag. In thisexample, office 230 does not have any sensors; for example, it may beused for purposes that do not involve the presence of patients.

In some embodiments, only the physician might wear an ID if his or heravailability primarily affects a patient's waiting time. If more thanone person wears an identifier, each of the identifiers may optionallyexpose or transmit a unique parameter. The parameter may include thewearer's role (“Doctor”), name (“Dr. Smith”), or any other encodableinformation linking the detected ID with its wearer. Such identificationparameters allow the sensor to record who is entering or exiting aservice location as well as when they enter or exit.

In some embodiments, assistant 202 also wears an ID, distinguishable bythe sensor(s) as assistant's identifier 221. As illustrated, assistant'sidentifier 221 may be in position to be detected by door sensor 223 inwaiting room 220. Door sensor 223 may activate door alert 227 to keeppatients from inadvertently leaving with their IDs. Alternatively, doorsensor 223 may simply record entry and exit of ID-wearers through themain office door. Door sensor 223 is logged by remote processor 234,which has a dedicated clock 235 and transmitter/receiver 236. In someembodiments, remote processor 234 is a hub processor for multiplesensors.

Patient 201, who has the current appointment, waits in service location210, an exam room. Optionally, patient 201 may wear a patient'sidentifier 211. Patient ID 211 may help locate the patient in the officeif there is any confusion about where he or she is. Logging patient ID211's interactions with door sensor 223 may also isolate the variable ofpatient arrival time if the sensor data on appointment timing is to beanalyzed.

Also in exam room 210 is an exam-room sensor 213. As illustrated,exam-room sensor 213 is part of a self-contained sensor module 205,another optional configuration for location sensors. Also in sensormodule 205 are dedicated sensor processor 214, dedicated clock 215, andsensor transmitter/receiver 216.

Delays and other events logged by sensors may trigger alerts on officeemployees' devices (mobile or not). For practices that emphasize humancontact, that notification may be sufficient; an employee would thenpersonally contact a patient with a delayed upcoming appointment andexplain options. By contrast, in a practice that prefers to reachpatients via technology may use an embodiment that sends schedulingupdates to device 206 accessed by upcoming patient 204, a holder of alater appointment.

With reference to FIG. 2B, shown is a diagram of detection of a passivereadable ID. ID 231B does not have its own power source. Sensor 213Bemits signal 214B, which impinges on ID 231B and is returned as returnsignal 215B. For example, ID 231B may be an RFID tag that, when withinrange of sensor 213B, takes power 214B from sensor 213B and uses it toemit its own signal 215B for detection by sensor 213B. In someembodiments, sensor 213B may emit signal 214B as pulses in predeterminedintervals to periodically check for a return signal 215B. As long as ID231B is in range, a return signal 215B will be periodically sent to thesensor 213B. By emitting a signal 214B in interval pulses may result inreduced power used as compared to emitting a continuous signal.

As another example, ID 231B may be a bar or QR code and sensor 213B mayinclude a scanning laser. The laser beam 214B (e.g., an eye-safelow-power infrared laser) is reflected or scattered from a coded pattern(e.g., a barcode or QR code) on ID 231B. The reflected or scatteredlight goes back to sensor 213B as return signal 215B. In someembodiments, sensor 213B may emit laser beam 214B in predeterminedintervals. As long as a return signal 215B is detected by sensor 213B ata regular interval, it can be determined that the ID 231B is withinrange. By emitting laser beam 214B in predetermined intervals may resultin reduced power used as compared to emitting a continuous signal.

With reference to FIG. 2C, shown is a diagram of detection of an emittedsignal from an active beacon ID. ID 231C may have its own power sourceenabling it to independently emit signal 215C toward sensor 213C. Insome embodiments, ID 231C may emit signal 215C toward sensor 213C inpulses at predetermined intervals. As long as a signal is detected bysensor 213C at a regular interval, it can be determined that the ID 231Cis within range. By emitting a signal in interval pulses may result inreduced power used as compared to emitting a continuous signal.

For example, beacons available at the time of this writing havedimensions on the order of 5-10 cm (2-4″), weights of less than 1 ounce,and line-of-sight ranges of a few centimeters to a few hundred meters,depending partially on whether their signals are Bluetooth™, BluetoothLow Energy (BTLE)™, ANT+™, IEEE 802.22™, IrDA™, NFC™, RFID™, Wi-Fi™,ZigBee™, wireless USB or HART, or some other signal type. Some activebeacons have built-in sensors for motion, light, magnetic fields, heat,and other quantities. A beacon with a built-in sensor could potentiallyfunction as either a beacon or a sensor, so that only one type of unitneeds to be ordered, deployed, and tracked. Some active beacons withbuilt-in processors and memory may be reprogrammed to change theirsignal characteristics, either to uniquely identify particular beaconsor to avoid interference with medical equipment. Such beacons may, forexample, be shared by employees whose shifts do not overlap or patientswhose appointments do not overlap. In either case, beacon 231C may bereprogrammed between uses to transmit the identifying parameter of thenext wearer rather than the preceding one.

In some embodiments, ID 231C may comprise a user device, such as medicalprofessional mobile device 1301, further described below. In someembodiments, sensor 213C may emit signal 215C toward ID user device231C. Upon detecting signal 215C, device 231C may determine that the ID231C is within range of sensor 213C. In some embodiments, sensor 213Cmay emit signal 215C toward ID 231C in pulses at predeterminedintervals. As long as a signal is detected by ID 231C at a regularinterval, it can be determined that the ID 231C is within range. Byemitting a signal in interval pulses may result in reduced power used ascompared to emitting a continuous signal.

With reference to FIG. 2D, shown is one type of sensor signal from whichentry and exit times may be derived. The sensor emits a signal 209D aslong as it detects an ID in range, and emits no signal (at least, nosignal associated with that particular ID) while the ID is out of range.The processor will read upward transition 207D as an entry and downwardtransition 218D as an exit.

In some embodiments, the sensor may emit a pulse at a predeterminedinterval as long as it detects an ID in range. For example, the sensormay periodically check for an ID at the predetermined interval and emitsa pulse if an ID is detected. As long as a pulse is emitted at a regularinterval, it can be determined at the processor that the ID is withinrange. If no ID is detected, then no pulse is emitted and the regularinterval of emitted pulses will be broken and it can bet determined thatthe ID is no longer within range. By emitting a signal in intervalpulses may result in reduced power used as compared to emitting acontinuous signal.

With reference to FIG. 2E, shown is another type of sensor signal fromwhich entry and exit times may be derived. The sensor sends a firstpulse 209E at time 207E when an ID comes within the sensor's range,emits no signal associated with that particular sensor while it remainsin range, then emits a second pulse at time 218E in response to the IDmoving out of the sensor range. In some embodiments, it may bepreferable to conserve beacon power; this schema uses significantly lesspower than emitting a signal continuously as in FIG. 2D. Distinguishingbetween entry and exit may be done via pulse length, as here, butalternatively by frequency, number of pulses, attack/release waveform,or the like.

With reference to FIG. 3, shown is a swim-lane diagram of propagatingdelays in appointments. This figure graphically represents theappointment routine described with reference to FIG. 1. A single sensorin the exam room monitors the progress of the appointment. At time 311,the assistant (long-dash line 302) brings the patient (solid line 301)into the exam room. After some time taking vital signs and the like,assistant 302 leaves the exam room at time 321, leaving patient 301 inthe exam room waiting for the physician. The physician (short-dash line303) enters the exam room at time 331, performs the exam, and leaves attime 341.

Horizontal fine solid lines 311, 321, 331, 341 and 351 represent localtimes logged when actual entries or exits are detected. Therefore, theycoincide with times at which the thicker lines representing thelocations of physician 303, assistant 302, and patient 301, crossbetween the “Out of Exam Room” lane (i.e., out of the detection range ofan exam-room sensor) and the “In Exam Room” line (i.e., in thedetectable range of the exam-room sensor). By contrast, horizontal finedotted lines 310, 320, 330, and 340 represent the scheduled entry andexit times. These times are stored in advance when the day's schedule isprepared, then retrieved to calculate a delay after each correspondingactual entry or exit occurs. For example, assistant 302 was scheduled toescort the patient into the exam room at time 310, but did not actuallydo so until time 311; the appointment is already running behindschedule.

In this example, delays propagate: every subsequent delay is either thesame length or longer than the immediately previous delay. Besidescomputing the delay between the scheduled and actual events, someembodiments of the process compare the delay to a stored threshold 305.Thresholding prevents excess notifications of employee and patientdevices when the delay is deemed too small to cause patients ofemployees to change his or her plans. Digital clocks can measure delaysof tiny fractions of a second, but humans, depending on the situation,may consider delays of less than a few minutes—or even delays of lessthan ½ hour—too small to warrant rescheduling the appointment. Setting athreshold 305 allows employees and upcoming patients to go about theirday without being distracted by alerts about delays too small to causeconcern.

FIGS. 4A-4C illustrate examples of flow sequences of processes forestimating delays for a medical appointment. The processes shown in eachof the figures can be used alone or together, depending on theapplication. For instance, the process shown in FIG. 4A can be usedalone in some examples, whereas, FIGS. 4A-4C can be combined in otherexamples. In some aspects, the notification system can be viewed as avirtual waiting room. The system tracks when appointments are runninglate and the system informs an upcoming patient that their appointmentis delayed and that they should delay arrival by a certain amount oftime.

With reference to FIG. 4A, shown is a flow sequence illustrating oneexample of a process for estimating delays for a medical appointment. Inthis example, delays in the schedule are estimated based on the timethat a medical assistant (or nurse) begins an appointment with apatient. According to various embodiments, scheduling times, activityand location tracking, event monitoring, and other triggers pertinent tomaintaining on-time scheduled appointments are referred to herein asscheduling information. In this process, estimating delays for a medicalappointment 400A begins with logging a location and time when a medicalassistant begins an appointment with a patient at 401A. Next, thislogged location and time is compared to a schedule at 403A. Thisschedule includes the patients and times for their appointments for thecurrent day. Based on this comparison, a determination is made whetherthe appointment is on time or substantially delayed at 405A. Forinstance, if the time that the medical assistant begins the appointmentis less than thirty (30) minutes later than the scheduled time for thispatient, the appointment can be categorized as being on time and theprocess ends. If the time that the medical assistant begins theappointment is thirty (30) minutes or more past the scheduled time forthis patient, then the appointment can be considered to be substantiallydelayed and the process continues at 407A. Although thirty (30) minutesis used in this example to determine whether the appointment is on time,any amount of time can be used. In some examples, this amount of timecan be set by a particular medical professional based on theirpreferences and office procedures.

In the present example, if the appointment is delayed thirty (30) ormore minutes, a determination is then made whether the appointment isunacceptably behind schedule at 407A. For the sake of this example, two(2) hours is used as a measure of when an appointment is unacceptablybehind schedule. Appointments unacceptably behind schedule will notleave enough time for upcoming appointments, and consequently, willrequire that the upcoming appointments be rescheduled. Although two (2)hours delay is used as the threshold for determining when upcomingappointments need to be rescheduled, any amount of time can be useddepending on the particular application of the system. For instance,certain physicians may want to decrease this time based on theirallotted examination times or to generally increase patientsatisfaction.

In the current example, if the delay is less than two (2) hours, thendelays for upcoming appointments are then estimated and these upcomingpatients are notified of these delays at 409A. For these upcomingpatients, the delay is between thirty (30) minutes and two (2) hoursbased on the current patient. In some examples, the delay can bepropagated through the schedule equally. Specifically, if the currentappointment is behind forty (40) minutes, then all of the upcomingappointments can be shifted forty (40) minutes later. However, in someexamples, each subsequent appointment can be shifted a certain amount inaddition to this forty (40) minutes if the system estimates that thephysician will incur additional delays from the subsequent appointments.Once the delay is estimated for the upcoming patients, the patients arethen notified.

According to various embodiments, upcoming patients are notified at 409Ausing their contact information. As described in more detail with regardto FIG. 11, this contact information can be stored in a database andaccessed by the notification system. This contact information can bekept separate from patient medical records, in order to avoid anyprivacy concerns regarding the federal Health Insurance Portability andAccountability Act of 1996 (HIPAA) or similar medical privacy laws inother nations. Specifically, the notification system accesses thecontact information for upcoming patients, such as a phone number. Insome examples, the notification system sends a text message to theupcoming patients notifying them of the expected delay and a later timethat they should arrive. For instance, an upcoming patient originallyscheduled for a two o'clock appointment may receive the followingmessage: “Dear Jane, your appointment originally scheduled for 4:00 pmtoday with Dr. Smith is running behind schedule. Could you please arriveat 4:45 pm instead? Sorry for the delay. Thank you for yourunderstanding.” Alternatively, the notification system can send avoicemail or email to upcoming patients, depending on factors such asthe patients' contact preferences and the office infrastructure.According to various embodiments, scheduling information such as medicalprofessional location tracking, appointment start triggers, eventmonitoring, etc., are cryptographically separated from HIPAAinformation.

According to various embodiments, medical professional activities,movements, and locations can be automatically or manually detected toallow improved appointment scheduling. For example, appointment starttimes can be manually or automatically triggered when a physician entersor a room and characteristics of the appointment can be used todetermine whether later appointments need to be adjusted. In particularembodiments, mechanisms for tracking physician or other medicalpersonnel activities, movements, and locations for schedulingappointments are firewalled from systems managing patient medical data.In some examples, different encryption mechanisms are used to encryptHIPAA data and scheduling information so that access to one system doesnot permit access to another system. In other examples, differentnetworks such as different virtual networks or different physicalnetworks are used to transport the different types of data. According tovarious embodiments, patient medical data is encrypted during bothstorage and transmission using a different mechanism from medicalpersonnel tracking data.

In the present example, if the delay is two (2) hours or more, then adetermination is made whether some or all of the upcoming patients forthe day need to be rescheduled. The patients that need rescheduling arethen notified at 411A and are offered an opportunity to reschedule theirappointments. For instance, if the physician is behind two hours, butcan cancel two upcoming appointments and be back on schedule withsubsequent patients, these two appointments may need to be rescheduled.In some cases, the schedule can be rearranged to cause as fewreschedules as possible. In some examples, the option to reschedule canbe offered through the text message, email, or voice message. Forinstance, an interactive sequence can be presented to the patient toallow them to reschedule immediately. This can provide convenience forboth the patients and the front office. Specifically, in some examples,one or more alternative times can be offered to the patient and thepatient can select one. Once the patient is notified according to thedescribed process (or if no delay is found), the process either ends orcontinues as described in FIG. 4B, depending on the desired applicationof the system.

With reference to FIG. 4B, shown is a flow sequence illustrating anotherexample of a process for estimating delays for a medical appointment. Inthis example, delays in the schedule are estimated based on the timethat a physician begins an appointment with a patient. This process canbe used alone in some examples, or it can continue following the processdescribed above with regard to FIG. 4A.

In the present example, estimating delays for a medical appointment 400Bbegins with logging a location and time when the physician begins anappointment with a patient at 401B. Next, this logged location and timeis compared to a schedule at 403B. This schedule includes the patientsand times for their appointments for the current day. Based on thiscomparison, a determination is made whether the appointment is on timeor substantially delayed at 405B. For instance, if the time that thephysician begins the appointment is less than thirty (30) minutes laterthan the scheduled time for this patient, the appointment can becategorized as being on time and the process ends. If the time that thephysician begins the appointment is thirty (30) minutes or more past thescheduled time for this patient, then the appointment can be consideredto be substantially delayed and the process continues at 407B. Althoughthirty (30) minutes is used in this example to determine whether theappointment is on time, any amount of time can be used. In someexamples, this amount of time can be set by a particular medicalprofessional based on their preferences and office procedures.

In the present example, if the appointment is delayed thirty (30) ormore minutes, a determination is then made whether the appointment isunacceptably behind schedule at 407B. For the sake of this example, two(2) hours is used as a measure of when an appointment is unacceptablybehind schedule. Appointments unacceptably behind schedule will notleave enough time for upcoming appointments, and consequently, willrequire that the upcoming appointments be rescheduled. Although two (2)hours delay is used as the threshold for determining when upcomingappointments need to be rescheduled in the present example, any amountof time can be used depending on the particular application of thesystem. For instance, certain physicians may want to decrease this timebased on their allotted examination times or to generally increasepatient satisfaction.

In this example, if the delay is less than two (2) hours, then delaysfor upcoming appointments are then estimated and these upcoming patientsare notified of these delays at 409B. For these upcoming patients, thedelay is between thirty (30) minutes and two (2) hours based on thecurrent patient. In some examples, the delay can be propagated throughthe schedule equally. Specifically, if the current appointment is behindforty (40) minutes, then all of the upcoming appointments can be shiftedforty (40) minutes later. However, in some examples, each subsequentappointment can be shifted a certain amount in addition to this forty(40) minutes if the system estimates that the physician will incuradditional delays from the subsequent appointments. Once the delay isestimated for the upcoming patients, the patients are then notified. Insome examples, if multiple factors are used to determine scheduledelays, such as the time that the medical assistant begins theappointment and the time that the physician begins the appointment, thenonly one notification may be provided. For instance, a step can beincluded that determines whether a notification has already been sent tothis patient, and if so, then an additional notification will not besent. In other examples, updates to this notification with currentwaiting times and real-time appointment adjustments can be made asupdated delays are predicted.

According to various embodiments, upcoming patients are notified at 409using their contact information. As described in more detail with regardto FIG. 11, this contact information can be stored in a database andaccessed by the notification system. This contact information can bekept separate from patient medical records, in order to avoid anyprivacy concerns regarding the federal Health Insurance Portability andAccountability Act of 1996 (HIPAA). Specifically, the notificationsystem accesses the contact information for upcoming patients, such as aphone number. In some examples, the notification system sends a textmessage to the upcoming patients notifying them of the expected delayand a later time that they should arrive. For instance, a patient laterin the day scheduled for a two o'clock appointment may receive thefollowing message: “Dear Jane, your appointment originally scheduled for2:00 pm today with Dr. Smith is running behind schedule. Could youplease arrive at 2:45 pm instead? Sorry for the delay. Thank you foryour understanding.” Alternatively, the notification system can send avoicemail or email to upcoming patients, depending on factors such asthe patients' contact preferences and the office infrastructure.

In the present example, if the delay is two (2) hours or more, then adetermination is made whether some or all of the upcoming patients forthe day need to be rescheduled. The patients that need rescheduling arethen notified at 411B and are offered an opportunity to reschedule theirappointments. For instance, if the physician is behind two hours, butcan cancel two upcoming appointments and be back on schedule withsubsequent patients, these two appointments may need to be rescheduled.In some cases, the schedule can be rearranged to cause as fewreschedules as possible. In some examples, the option to reschedule canbe offered through the text message, email, or voice message. Forinstance, an interactive sequence can be presented to the patient toallow them to reschedule immediately. This can provide convenience forboth the patients and the front office. Specifically, in some examples,one or more alternative times can be offered to the patient and thepatient can select one. Once the patient is notified according to theprocess (or if no delay is found), the process either ends or continuesas described in FIG. 4C, depending on the desired application of thesystem.

In the present example, although both a location and time are loggedwhen the physician begins the appointment, it should be noted that insome embodiments, the location need not be logged. For instance, if thepatient and time are adequately identified and logged, then the locationdoes not need to be logged in order to compare the actual appointmenttime with the scheduled appointment time. According to various examples,the location log can be used to determine when a physician is seeing aparticular patient. Specifically, in cases where location logging isautomated, such as with sensors, GPS, or the like, then the location canprovide information about which patient a physician is currently seeing.

With reference to FIG. 4C, shown is a flow sequence illustrating anotherexample of a process for estimating delays for a medical appointment. Inthis example, delays in the schedule are estimated based on the timethat a physician ends an appointment with a patient. This process can beused alone in some examples, or it can continue following the processdescribed above with regard to FIGS. 4A and/or 4B.

In the present example, estimating delays for a medical appointment 400Cbegins with logging a location and time when the physician ends anappointment with a patient at 401C. Next, this logged location and timeis compared to a schedule at 403C. This schedule includes the patientsand times for their appointments for the current day. Based on thiscomparison, a determination is made whether the appointment is on timeor substantially delayed at 405C. For instance, if the time that thephysician ends the appointment is less than thirty (30) minutes laterthan the scheduled time for this patient plus the allotted duration ofthis type of appointment, the appointment can be categorized as being ontime and the process ends. If the time that the physician ends theappointment is thirty (30) minutes or more past the scheduled time forthis patient plus the allotted duration of this type of appointment,then the appointment can be considered to be substantially delayed andthe process continues at 407C. Although thirty (30) minutes is used inthis example to determine whether the appointment is on time, any amountof time can be used. In some examples, this amount of time can be set bya particular medical professional based on their preferences and officeprocedures.

In the present example, if the appointment is delayed thirty (30) ormore minutes, a determination is then made whether the appointment isunacceptably behind schedule at 407C. For the sake of this example, two(2) hours is used as a measure of when an appointment is unacceptablybehind schedule. Appointments unacceptably behind schedule will notleave enough time for upcoming appointments, and consequently, willrequire that the upcoming appointments be rescheduled. Although two (2)hours delay is used as the threshold for determining when upcomingappointments need to be rescheduled in the present example, any amountof time can be used depending on the particular application of thesystem. For instance, certain physicians may want to decrease this timebased on their allotted examination times or to generally increasepatient satisfaction.

In this example, if the delay is less than two (2) hours, then delaysfor upcoming appointments are then estimated and these upcoming patientsare notified of these delays at 409C. For these upcoming patients, thedelay is between thirty (30) minutes and two (2) hours based on thecurrent patient. In some examples, the delay can be propagated throughthe schedule equally. Specifically, if the current appointment is behindforty (40) minutes, then all of the upcoming appointments can be shiftedforty (40) minutes later. However, in some examples, each subsequentappointment can be shifted a certain amount in addition to this forty(40) minutes if the system estimates that the physician will incuradditional delays from the subsequent appointments. Once the delay isestimated for the upcoming patients, the patients are then notified. Insome examples, if multiple factors are used to determine scheduledelays, such as the time that the medical assistant begins theappointment and/or the time that the physician begins the appointment,then only one notification may be provided. For instance, a step can beincluded that determines whether a notification has already been sent tothis patient, and if so, then an additional notification will not besent. In other examples, updates to this notification with currentwaiting times and real-time appointment adjustments can be made asupdated delays are predicted.

According to various embodiments, upcoming patients are notified at 409Cusing their contact information. As described in more detail with regardto FIG. 11, this contact information can be stored in a database andaccessed by the notification system. This contact information can bekept separate from patient medical records, in order to avoid anyprivacy concerns regarding the federal Health Insurance Portability andAccountability Act of 1996 (HIPAA). Specifically, the notificationsystem accesses the contact information for upcoming patients, such as aphone number. In some examples, the notification system sends a textmessage to the upcoming patients notifying them of the expected delayand a later time that they should arrive. For instance, an upcomingpatient scheduled for a two o'clock appointment may receive thefollowing message: “Dear Jane, your appointment originally scheduled for2:00 pm today with Dr. Smith is running behind schedule. Could youplease arrive at 2:45 pm instead? Sorry for the delay. Thank you foryour understanding.” Alternatively, the notification system can send avoicemail or email to upcoming patients, depending on factors such asthe patients' contact preferences and the office infrastructure.

In the present example, if the delay is two (2) hours or more, then adetermination is made whether some or all of the upcoming patients forthe day need to be rescheduled. The patients that need rescheduling arethen notified at 411C and are offered an opportunity to reschedule theirappointments. For instance, if the physician is behind two hours, butcan cancel two upcoming appointments and be back on schedule withsubsequent patients, these two appointments may need to be rescheduled.In some cases, the schedule can be rearranged to cause as fewreschedules as possible. In some examples, the option to reschedule canbe offered through a text message, email, voice message, or pushnotification. For instance, an interactive sequence can be presented tothe patient to allow them to reschedule immediately. This can provideconvenience for both the patients and the front office. Specifically, insome examples, one or more alternative empty appointment time slots canbe offered to the patient and the patient can select one. Once thepatient is notified according to the process described (or if no delayis found), the process ends.

In the present example, although both a location and time are loggedwhen the physician ends the appointment, it should be noted that in someembodiments, the location need not be logged. For instance, if thepatient and time are adequately identified and logged, then the locationdoes not need to be logged in order to compare the actual appointmenttime with the scheduled appointment time. According to various examples,the location log can be used to determine when a physician is seeing aparticular patient. Specifically, in cases where location logging isautomated, such as with sensors, GPS, or the like, then the location canprovide information about which patient a physician is currently seeing.

In some embodiments, multiple processes described with regard to FIGS.4A-4C can be used to provide feedback to the physician about scheduleefficiencies or inefficiencies. For instance, data can be gathered andstatistics can be generated for a particular day showing how manyappointments were delayed, by how much, and whether the delays werecaused by medical assistant delay, physician delay, or appointments thatran longer than the allotted time for the type of exam that wasperformed. In addition, statistics can be provided over periods oftimes, from days to months to years, depending on the time specified. Insome examples, graphs and/or charts can be provided that show trends.Furthermore, suggestions can be provided based on the data provided,such as whether actual examination times are exceeding the allottedtimes, and by how much. Percentages can be provided showing how muchoverrun is occurring and how often. Suggestions such as extending theallotted times for examinations or spacing appointments further apartmay be provided.

With reference to FIG. 5, shown is a swim-lane diagram of compensateddelays in appointments. FIG. 3, discussed above, illustrated propagatingdelays; for successive entries or exits, the delay either remainedconstant or increased. Delays may not always propagate, however; a delaymay be “made up” if a process takes less than the expected time (e.g., apatient arrives with a questionnaire already filled out) or is cancelledaltogether (e.g., if a patient “no-shows” or reschedules only a fewhours before the appointment). Assistant 502 is scheduled to bringpatient 501 to the exam room. at time 510, but does not actually do sountil later time 511; the appointment is running behind schedule. Aftersome time taking vital signs and the like, assistant 502 is scheduled toleave the exam room at time 520, but does so at earlier time 521 so thatnow the appointment is ahead of schedule. Physician 503 is scheduled toenter the exam room at time 530, but does not do so until later time531, so that the appointment is behind schedule again. However,physician 503 leaves the exam room at time 341, which is equal toscheduled time 540, putting the appointment back on schedule.

The following appointment (and, barring further delays, the appointmentsfollowing it) may actually start on time. Meanwhile, though, a delaymessage may have been transmitted at time 511 (or possibly not if thissmall delay was sub-threshold. Depending on the embodiment, a“back-on-schedule” notification might have been transmitted at time 521,or the system may be programmed to ignore on-schedule events. Anotherdelay message may have been transmitted at time 531 (a longer delaylikely to exceed the threshold) and perhaps one or more patients decidedto reschedule, but at time 541 there was no longer a delay, therefore noactual need to incur the added overhead of the rescheduling.

Identification of gating events can smooth out such fluctuations inexpected delays. After leaving the exam room at time 541, physician 503is now free to see another patient (or will be after an allotted time to“wrap up” the current appointment). Thus the physician's exit from theexam room at time 541 may be the “gating event” that determines the endof the appointment, making it possible to estimate the beginning of thenext appointment. Therefore, in some embodiments the system may log allentries and exits, with or without comparing the logged time with thescheduled time, but it may refrain from transmitting delay messagesexcept when a gating event occurs.

With reference to FIG. 6, shown is a flow diagram of an operation thatmay be implemented as software. Operation 600 may include detecting aposition or motion of a first identifier within a sensor range, whereinthe sensor range at least partially covers a first service location. Achange in the sensor signal, which may include being turned on or off,triggers operations 601 a-c, which may include logging a local time 601a, optionally logging a sensor location 601 b (e.g., if there aremultiple sensors to distinguish or the sensor moves from one servicelocation to another), and logging a first identifying parameter 601 c ofthe first identifier (to identify the particular wearer) in response toan entry of the first identifier into the sensor range or an exit of thefirst identifier out of the sensor range.

Optional decision 610 may include determining whether the logged entryor exit is a gating event. If so, or if the gating-event determinationis omitted, operation 611 may include retrieving a scheduled time of theentry or the exit during a first appointment and subtracting the firstscheduled time from the local time to estimate a first delay.

Optional decision 620 may include comparing the first delay to athreshold. If the first delay is greater than the threshold, operation621 may include estimating the delay of upcoming patients' appointmentsby adding the first delay to the second scheduled time to compute theexpected time of the delayed appointment. Operation 623 may includenotifying a first device that the second appointment will be delayeduntil the expected time and optionally display a selectable “keep”option and a selectable list of open appointment slots on the firstdevice after the notifying. The device may be an employee device, anupcoming patient's device, or both. Selection may be done by typing,touching, clicking, voice, or any other suitable way to choose from aset of options using the device.

Optional decision 630 may calculate whether the delayed time of theday's last appointment has become so late that the office will closebefore the appointment is completed. If so, the holder of thatappointment may be offered rescheduling options but no “keep” option inoperation 631. Operation 625 updates the stored schedule for the rest ofthe day to account for the currently expected delay. The system mayrespond to an upcoming patient's selection of a “keep” option byreplacing the patient's current scheduled time with the expected time ofthe delayed appointment.

Decision 640 determines whether an upcoming patient has rescheduled and,if so, executes an updating operation 625 replacing the patient'scurrently scheduled appointment with the rescheduled appointment. Insome embodiments, this step may be executed any time any patientrequests a reschedule, rather than only in response to a delaynotification. Finally, decision 650 determines whether the lastappointment of the day has been finished; if not, operation 612 returnsthe system to monitoring the sensor(s) whenever there is no reason for adelay notification, such as when the most recent event was not a gatingevent per decision 610 or was not an above-threshold delay per decision620. If it is determined to be the last appointment at decision 650, thesystem responds by stopping the process, ceasing to monitor thesensor(s)

FIGS. 7A-7C illustrate examples of delay notifications displayed ondevice screens. Non-display notifications such as voice-mails are alsowithin the scope of some embodiments.

With reference to FIG. 7A, shown is a cell phone displaying a textmessage. Most cell phones 701 are able to display a text message 703,which may include details 705 of open appointment slots for reschedulingand enable the user to communicate a choice using the keypad.

With reference to FIG. 7B, shown is a smartphone displaying a pushnotification from an installed application (“app”). A smartphone 711 mayalso receive voicemail and text messages, but may include the additionalpossibilities of push notifications 713 or dedicated apps with graphicuser interfaces (GUIs). A GUI may display “Keep” option 715 and openslots 717 as buttons or other clickable or touchable features.

With reference to FIG. 7C, shown is a desktop computer displaying analert. As well as upcoming patients, employees of the medical office canalso benefit from delay notifications by organizing their tasks andbreaks around the times when the appointments are likely to begin andend, rather than when the appointments were originally intended to beginand end.

With reference to FIG. 8, shown is a swim-lane diagram of multipleentries and exits of participants in a single appointment. Previously itwas proposed that the physician's exit from the exam room might be thebest indicator of the appointment being over, and therefore a goodchoice of a gating event. However, if the physician exits the exam roommore than once during a single appointment, only the last such exit ispreferably used to calculate the delay.

For example, physician 803 exits the exam room at time 842, but onlytemporarily. Physician 803 may need to answer an urgent question, fetchan injectable, or the like. Shortly thereafter, physician 803 re-entersthe exam room, finishes his or her part of the appointment, and re-exitsat time 841. Meanwhile, the sensor detects exit 842 and may compute andcommunicate a delay based on exit time 842. Upon detecting the secondexit 841, the system may compare the local time with the NEXT scheduledphysician-exit time during the following appointment, which will yieldan inaccurate result.

Likewise, assistant 802 may enter the exam room at time 811, collectpreliminary information for the physician, and leave at time 821, thenenter again to answer logistics questions for an upcoming procedureafter the physician exits, and exit again at time 822. If this happensin some types of appointments but not in others, some systems mightchoose the wrong scheduled time to compare to the second exit.

Patient 801's exit from the exam room might be a better choice of gatingitem; the sensor would detect patient 801's exit at time 861, thenretrieve the log entry for the immediately preceding physician 803 exitat time 841 and calculate the delay from it. In this process, thepatient's exit is a “confirming event” signaling that the appointment isover and the physician's most recent exit is therefore the gating event.However, even patient 801 does not necessarily stay in the exam room forthe entire appointment. For example, the patient may exit at time 862 togive a sample or answer an administrative question, and then return tothe appointment.

Looking further ahead, patient 801's appointment must definitely be overwhen the next patient 811 enters the exam room at time 871. Therefore, asystem can avoid being “confused” by multiple entries and exits ofparticipants in a single appointment by using the entry of the nextpatient as a confirming event, retrieving the most recent physician exitbefore time 871, and using it to calculate the delay. This preventspatient 811 from getting updates on delays generated during patient801's appointment. However, because those updates would likely have beenexcessively short notice for patient 811 to change plans, the impact isminimal.

With reference to FIG. 9, shown is a flow diagram of a processaccommodating multiple entries and exits. An appointment begins withoperation 900 with a first patient entering the exam room. Operation 901may include logging entries and exits detected by the sensor.

After each logging operation, the system decides at decision 910 whetherthe most recent event confirms that the first patient's appointment hasended. In this example, the confirming event is the entry of a secondpatient into the exam room. If not, the system may return to operation910 of monitoring and logging, rather than performing delaycalculations. If so, operation 911 may include identifying the mostrecent event as a confirming event, therefore the last previousphysician exit was the gating event. Operation 913 may includeretrieving the local time and the scheduled time of the gating event.

Decision 920 determines whether the difference between the gatingevent's local time and its corresponding scheduled time is greater thana stored threshold. If not, the system may return to operation 910 ofmonitoring and logging, rather than performing delay calculations. Ifso, operation 921 may include estimating a delay for upcomingappointments, followed by operation 923 of notifying devices, offeringreschedule options, and updating the schedule.

FIGS. 10A-10C illustrate an embodiment in which a patient carries asensor and the service locations, physicians, and assistants carryactive beacons. This type of system tracks the service locations that apatient visits—helpful in practices where patients spend time intreatment rooms, sample collection rooms, the physician's office orconference room, or elsewhere besides an exam room. The system alsotracks the time that physicians and assistants spend in proximity to thepatient, which may be helpful in settings where patients are examined,tested, or treated in cubicles or bays or at counters that are small andclose together with partial dividing walls or none at all.

With reference to FIG. 10A, shown is an example of a medical officefloor plan. Optionally, when patient 1001 checks in at reception 1010,office staff member 1006 may use machine 1016 to program an identifyingparameter into sensor 1013 that is unique to the patient or theappointment. Sensor 1013 has a sensor range 1043 which in someembodiments may be only 1-2 m (3-6′) and a built-in clock 1015 or accessto some other clock signal.

Assistant 1002 wears beacon 1021 emitting signal 1026, which is detectedby sensor 1013 when assistant 1002 escorts patient 1001 to exam room1020. In some embodiments, signal 1026 may include an identificationparameter associates with the assistant wearing it. When patient 1001enters exam room 1020, sensor 1013 detects exam-room beacon signal 1024from exam-room location beacon 1022. Signal 1024 may also include anexam-room identification parameter. When assistant 1002 exits the examroom, sensor 1013 stops detecting signal 1026 but continues detectingsignal 1024 because patient 1001 is still in exam room 1020.

Meanwhile, physician 1003 in office 1030 wears physician's beacon 1031transmitting physician's beacon signal 1033 while office location beacon1023 transmits office beacon signal 1034. When physician 1003 entersexam room 1020, sensor 1013 will begin to detect physician's beaconsignal 1033. If physician 1003 then escorts patient 1001 into office1030 for a conference, sensor 1013 will stop detecting exam-room beaconsignal 1024 and begin detecting office beacon signal 1034.

In some embodiments, patient 1001 may return sensor 1013 to member ofoffice staff 1006 when the appointment ends. The timing informationlogged by sensor 1013 may be uploaded to storage via machine 1016 orsome other device. Note that this approach may obviate the need forgating-even and confirming-event capture and the accompanyingcalculations; when the patient returns sensor 1013, the appointment maybe over by definition. Optionally, delay data over a span of time suchas a week or a month may be analyzed to diagnose any frequent causes ofdelay.

With reference to FIG. 10B, shown is a display interface 1051 forprogramming a patient sensor at the beginning of an appointment. Thepatient's record number, name, and/or appointment time may be used toidentify the log entries uploaded later. The patient arrival time mayhelp derive how many and what lengths of delays are generated whenpatients arrive late.

With reference to FIG. 10C, shown is a display interface 1052 foruploading data on patient entry and exit times a patient sensor at thebeginning of an appointment. Any or all of identifying parameters 1054may be used to label the data in a database.

With reference to FIG. 11, shown is a diagrammatic representation of oneexample of a database designed to store patient information. Asdescribed above with regard to FIGS. 4A-4C, contact information forpatients is retrieved by the notification system when upcoming patientsare to be notified of a delay in their appointment times. However, inorder to avoid any privacy concerns regarding HIPAA, the notificationsystem is limited to retrieving contact information that is not relatedto patient-sensitive information.

In the present embodiment, database 1100 includes patient appointmentinformation 1101 and patient medical records 1115. Patient appointmentinformation 1101 includes information for numerous patients such as name1103, date of birth 1105, account number 1107, appointment time(s) 1109,and contact information 1111. The contact information 1111 can includeinformation such as phone number(s) (for text and/or voicemail), emailaddress, mailing address, and residence address. Additional or differentinformation can be included, depending on the intended use of thedatabase. However, patient appointment information is intended toinclude information that can be accessed by a scheduling or frontoffice, without concerns about privacy under HIPAA. For example, patientappointment information 1101 may be accessed by an app 1135 onoffice-employee devices over a network 1137.

In some embodiments, appointment change status information 1141 may bestored in the non-HIPAA portion of the same database 1100. Appointmentchange status information 1141 may include, without limitation, lookuptable 1143 of the latest appointment times held by each patient; currentdelay information 1145 collected by sensors; available open slots 1147for patients who opt to reschedule their appointments; and staff and/orhelpdesk contact info 1149 for patients who need help with appointmentschedule issues. Appointment change status information 1141 may beaccessed by an app 1155 on patients' devices over a network 1157, whichmay or may not be the same as network 1137. In some embodiments,patients' option choices (e.g., to keep a delayed appointment or toreschedule) are received in database 1100 over network 1157.

In the present example, patient medical records 1115 are protected by afirewall 1102 that prevents inadvertent or unauthorized access topatient information protected under HIPAA. The patient medical records1115 include information for numerous patients such as diagnoses 1117,medications 1119, physician's notes 1121, confidential communications1123, and lab results 1125. Additional or different information can beincluded depending on the preferences of the physician or practice. Thepatient medical records 1115 may include sensitive information that isprotected under HIPAA privacy laws. Accordingly, this information mustbe handled carefully and access to it must be restricted to authorizedpeople and systems.

According to various embodiments described herein, a medical schedulingmanagement system notifies upcoming patients of a delay in theirappointment times by accessing patient appointment information such asname 1103, appointment time 1109, and contact information 1111. In someexamples, the notification system is implemented as an app for mobiledevices. This app 1135 retrieves 1137 patient appointment information topredict schedule delays, such as by retrieving appointment times 1109and comparing these appointment times 1109 to real-time appointmentprogress for a particular physician. In addition, this app 1135retrieves contact information 1111 and names 1103 for patients that areto be notified of upcoming schedule delays. As indicated in the figure,the app 1135 does not have access to patient medical records 1115, andis prevented from accessing these patient medical records 1115 byfirewall 1102. Although this example is described in the context of anapp that can be implemented on one or more smartphones, mobile devices,etc., it should be recognized that this notification system can beimplemented over any computer system. For instance, an office-basedcomputer system can be updated manually by a medical assistant or otherpersonnel to reflect current appointment times and the system canoperate without any mobile devices.

As described in previous examples, a medical scheduling managementsystem can be used to predict delays for upcoming appointments andnotify upcoming patients of these delays. The medical schedulingmanagement system can be implemented in various ways. FIGS. 12 and 13illustrate two examples of configurations for medical schedulingmanagement systems. It should be noted that although two particularexamples are described, modifications and adjustments can be made withinthe scope of this disclosure.

With reference to FIG. 12, shown is a diagrammatic representation of oneexample of a medical scheduling management system. The medicalscheduling management system 1200 shown includes identifier 1250,location sensor 1201, clock 1202, memory 1203, medical scheduleprocessor 1205, delay log interface 1207, employee interface 1213,employee device(s) 1209, and patient notification interface 1211. Thelocation sensor 1201 is designed to detect when a medical professionalenters an examination room to conduct an examination of a particularpatient. Clock 1202 tracks the local time that is captured by processor1205 when sensor 1202 detects the appearance or disappearance of anidentifier. This location sensor 1201 can be implemented in numerousways. In one example, a medical professional wears an identifier 1250that is detectable in different areas of the office. The system is ableto detect when identifier 1250, such as an RFID, etc. is in proximity tothe location sensor. In some applications, there may be multipleidentifiers simultaneously detected by a sensor. The processor, byextracting identifying parameter 1251, can discern whose identifier wasdetected by sensor 1201. In some applications, there may be multiplelocation sensors in the system.

In other examples, the location sensor 1201 represents an inputinterface used by a medical assistant or other personnel to enter thelocation of the medical professional at a particular time. Specifically,location and time information can be entered manually into the system.In some instances, the location sensor 1201 represents an inputinterface used by the medical professional to indicate when a particularappointment has started. Specifically, location and time information canbe entered manually into the system. For instance, the next scheduledappointment may pop up or be otherwise selectable on a mobile device,and when the medical professional selects a button, the time is loggedand this time is compared with the scheduled time. In yet otherembodiments, the medical scheduling management system 1200 can beimplemented as an app on a mobile device, such as a smartphone. In theseexamples, the location sensor 1201 can implement technologies such asGPS or other location sensing systems. In some examples, the locationsensor 1201 can be omitted, such as when only the patients and times arelogged.

In the present embodiment, the medical schedule processor 1205 isdesigned to log the time when a medical professional enters anexamination room for a particular appointment and compare this time witha schedule to predict whether future appointments in the schedule willbe delayed. The schedule typically includes patients and times forappointments scheduled on a particular day. According to variousexamples, the schedule may not include any HIPAA information. The memory1203 is used to store data, which may include the present day's schedule1223 and stored thresholds 1233, store program instructions, andmaintain a local side cache. The program instructions may control theoperation of an operating system and/or one or more applications, forexample. In addition, display 1209 is used to allow a user to interactwith the system, such as through a monitor, screen, etc.

In the present embodiment, the notification interface 1211 is used tonotify upcoming patients if their appointments will be substantiallydelayed, as described in more detail with regard to FIGS. 4A-4C above.This notification interface 1211 is also designed to notify upcomingpatients if their appointments need to be rescheduled. In some examples,the notification interface 1211 is also designed to provide an optionfor these patients to reschedule their appointments. As described above,the notification interface 1211 contacts a patient device 1217 usingpatient contact information such as a phone number, email, etc. In someexamples, the notification interface 1211 notifies a patient via a textmessage. In other examples, the notification interface 1211 notifies apatient via a voicemail or email. Other notification modes can also beused, depending on the preferences of the patient and medical office.

In the present example, delay log interface 1207 allows data such asreal-time location and time information for appointments in-progress tobe transmitted to an appointment delay log 1219. This appointment delaylog 1219 is located in a separate location that may be accessed by otherdevices. For instance, if the medical scheduling management system 1200is implemented as an app on a mobile device, the appointment delay log1219 may include an office computer that is accessible to office staffand personnel. In other examples, the appointment delay log 1219 can belocated on a cloud drive. However, the delay log interface 1207 andappointment delay log 1219 can be omitted in some applications,depending on the needs of the practice.

As shown in the present embodiment, the medical scheduling managementsystem 1200 can interact with a patient appointment information database1215, such as the one shown and described with regard to FIG. 11.Patient appointment information database 1215 may include patientcontact information 1225 and open appointment slots 1235. In particular,the medical scheduling management system 1200 accesses the patientappointment information database 1215 when predicting delays, whennotifying upcoming patients by messaging their devices such as patientdevice 1217, and when notifying medical-office employees throughemployee interface 1213 via employee devices 1209. As mentioned withregard to FIG. 11, the information accessible in the patient appointmentinformation database 1215 is not data that is protected under HIPAA.

With reference to FIG. 13, shown is a diagrammatic representation ofanother example of a medical scheduling management system. In thisexample, the medical scheduling management system 1300 includes amedical scheduling management hub 1315 and one or more medicalprofessional mobile devices 1301. The medical professional mobile device1301 can be implemented as a mobile device, such as a smart phone,tablet, etc. In other examples, this mobile device 1301 can beimplemented as a wearable device such as a bracelet, fob, charm, clip,etc. In some embodiments, the medical professional mobile device 1301 isa specialized device with added security and firewall capabilities toseparate information that is protected under HIPAA, further describedwith reference to FIG. 11.

As shown, the medical scheduling management hub 1315 is implemented on acomputer such as a mobile device, office computer, server, etc. Thisserves as a “home base” for the system. In some examples, this hub 1315is implemented on a central office computer or on the cloud. In thepresent example, the medical professional mobile device 1301 includes alocation sensor 1303, memory 1305, processor 1307, display 1309, andnotification hub interface 1311. The location sensor 1303 is designed todetect when a medical professional enters an examination room to conductan examination of a particular patient. This location sensor 1303 can beimplemented in numerous ways. In one example, the location sensor isable to identify when the medical professional is in different areas ofthe office. In these examples, the location sensor 1303 can implementtechnologies such as GPS, RFID, Bluetooth, triangulation mechanisms,cameras, or other location sensing systems. In other examples, thelocation sensor 1303 represents an input interface used by the medicalprofessional to indicate when a particular appointment has started.Specifically, location and time information can be entered manually intothe system. For instance, the next scheduled appointment may pop up orbe otherwise selectable the mobile device 1301, and when the medicalprofessional selects a button, the time is logged and this time iscompared with the scheduled time. In some embodiments, the locationsensor 1303 can be omitted, such as when only patient and timeinformation are logged.

In the present example, the medical professional mobile device 1301includes memory 1305, which is used to store data and programinstructions and maintain a local side cache. The program instructionsmay control the operation of an operating system and/or one or moreapplications, for example. In some examples, the size of the memory 1305may be limited, as when most of the processing and storage of data isperformed at the medical scheduling management hub 1315. In addition,the processor 1307 may include limited processing of the data collected.For instance, the data collected may include the times and locations ofparticular appointments, and the processor can be used to format theinformation before sending it to the medical scheduling management hub1315. The limited memory 1305 and processor 1307 sizes and capabilitiesmay be appropriate especially in cases when the medical professionalmobile device 1301 is implemented as a wearable because the componentscan be smaller and more conveniently designed into a smaller casing tobe comfortably worn. In the present example, display 1309 is used toallow the medical professional to interact with the system, such asthrough a screen, touch screen, etc. As described above, the medicalprofessional may input data through this display 1309 and/or viewoptions through the display.

In the present example, the medical professional mobile device 1301 alsoincludes a notification hub interface 1311. This notification hubinterface 1311 is used to communicate with the medical schedulingmanagement hub 1315. In particular, data regarding real-time appointmentstart times are sent via the notification hub interface 1311 to themedical scheduling management hub 1315 via medical professional deviceinterface 1321. In some examples, the medical professional deviceinterface 1321 is used to send messages to the medical professionalmobile device 1301 via the notification hub interface 1311, such as “Hasthe Smith 1:10 pm appointment begun?”

In the present embodiment, the medical scheduling management hubincludes a medical schedule processor 1317 designed to log the time whena medical professional enters an examination room for a particularappointment and compare this time with a schedule to predict whetherfuture appointments in the schedule will be delayed. The scheduletypically includes patients and times for appointments scheduled on aparticular day. According to various examples, the schedule does notinclude any HIPAA information. The memory 1319 is used to store data andprogram instructions and maintain a local side cache. The programinstructions may control the operation of an operating system and/or oneor more applications, for example. In addition, display 1323 is used toallow a user to interact with the system, such as through a monitor,screen, etc.

In the present embodiment, the patient notification interface 1325 isused to notify upcoming patients if their appointments will besubstantially delayed, as described in more detail with regard to FIGS.4A-4C above. This notification interface 1325 is also designed to notifyupcoming patients if their appointments need to be rescheduled. In someexamples, the notification interface 1325 is also designed to provide anoption for these patients to reschedule their appointments. As describedabove, the notification interface 1325 contacts a patient 1345 usingpatient contact information such as a phone number, email, etc. In someexamples, the notification interface 1325 notifies a patient via a textmessage. In other examples, the notification interface 1325 notifies apatient via a voicemail or email. Other notification modes can also beused, depending on the preferences of the patient and medical office.

As shown in the present embodiment, the medical scheduling managementhub 1315 interacts with a patient appointment information database 1335,such as the one shown and described with regard to FIG. 11. Inparticular, the medical scheduling management hub 1315 accesses thepatient appointment information database 1335 when predicting delays andwhen notifying upcoming patients, such as patient 1345. As mentionedwith regard to FIG. 11, the information accessible in the patientappointment information database 1335 is not data that is protectedunder HIPAA.

Although FIGS. 12 and 13 describe particular configurations of medicalscheduling management systems, it should be recognized that variousconfigurations can be constructed within the scope of this disclosure.In addition, the system can be used to provide feedback to the physicianand/or practice to allow them to generate physician/examinationefficiency reports in some examples. For instance, the system cangenerate reports indicating the percentage of appointments that weredelayed and by how much they were delayed. In some cases, the reportscan be customizable to indicate factors such as whether certain types ofappointments are delayed more often, times of day when more appointmentsare delayed, days of the week or month when appointments are delayedmore often, etc. This feedback can be used by the physician to improvetheir care and service and become more efficient in their practice. Thiscan lead to more satisfied patients, a more pleasant experience for thepatients and medical professionals, and a higher rate of return for thephysician and practice.

These and other configurations of medical scheduling management systemsare further described in U.S. patent application Ser. No. 14/794,851titled MEDICAL SCHEDULING MANAGEMENT SYSTEM by Bullington et al., filedon Jul. 9, 2015; and U.S. patent application Ser. No. 14/794,852 titledPHYSICIAN EFFICIENCY ANALYSIS SYSTEM by Bullington et al., filed on Jul.9, 2015; and U.S. patent application Ser. No. 14/794,854 titled VIRTUALWAITING ROOM FOR MEDICAL APPOINTMENTS by Bullington et al., filed onJul. 9, 2015; and U.S. patent application Ser. No. 14/794,857 titledMEDICAL APPOINTMENT PROGRESS TRACKING by Bullington et al., filed onJul. 9, 2015; and U.S. patent application Ser. No. 15/333,087 titledAPPOINTMENT SCHEDULING MANAGEMENT SYSTEM by Bullington et al., filed onOct. 24, 2016. The above mentioned applications are incorporated byreference herein in their entirety and for all purposes.

In various embodiments, one or more components of a medical schedulingmanagement system, such as medical scheduling management system 1200,may be located within a single apparatus, such as sensor module 205. Insome embodiments, a sensor module 205 may comprise a lighting device,such as a light bulb.

With reference to FIG. 14, shown is a diagrammatic representation of anexample of a lighting system for medical scheduling management, inaccordance with one or more embodiments. In some embodiments, lightingsystem 1400 may be a light bulb that can be used in any room with anappropriate terminal. In some embodiments, lighting system 1400 maycomprise lighting element 1413. In some embodiments, lighting element1413 may be a component of lighting system 1400 which emits light forlighting a room, such as an examination room. For example, lightingelement 1413 may be a metal filament, such as tungsten, which is housedin a sealed, oxygen-free chamber. In another example, lighting element1413 may be a light emitting diode (LED) lighting system.

In some embodiments, lighting system 1400 may comprise a light fixtureand lighting element 1413 may be a light bulb that is used withinlighting system 1400. In some embodiments, lighting element 1413 may bean incandescent lamp with a wire filament. In further embodiments,lighting element 1413 may comprise a light emitting diode (LED) lampincluding one or more LED chips. In yet further embodiments, lightingelement 1413 may comprise a compact fluorescent lamp (CFL).

In various embodiments, lighting element 1413 may be connected tolighting system 1400 via a lighting interface 1408. For example, wherelighting system 1400 comprises a light bulb, such as an incandescentlight bulb, the lighting interface 1408 may comprise a base. Such basemay be configured to couple to a power source via one of variousstandard E27 screw, or other Edison screw coupling. The base may furtherbe configured with a bottom terminal contact for transferring electricalpower to a fuse lead-in to heat the filament lighting element 1413. Asanother example, where lighting system 1400 comprises an LED lightingsystem, lighting interface 1408 may comprise an anode lead and a cathodelead, which couple to a power source to provide electrical current tothe light emitting diode lighting element 1413.

In embodiments, where lighting element 1413 comprises a light bulb,lighting system 1400 may be configured to attach to a power source ofthe exam room at an electrical terminal. In other embodiments, lightingsystem 1400 may be electrically connected to the power source of theexam room. Such lighting system may include a lighting interface 1408comprising one or more different couplings for lighting element 1413,such as a standard E27 screw, other Edison screw coupling, etc.

In some embodiments, lighting system 1400 is located at the center of aroom, such as a medical examination room. Lighting fixtures aregenerally positioned in the center of a room. In various medicalsettings lighting fixtures are centrally positioned to provide optimallighting for examinations and/or procedures. For example, an examinationtable and/or chair may be located in the center of an examination roomwith lighting system 1400 positioned above on the ceiling. Since alighting structure in a medical examination room may be centered aboutthe location of a patient during an examination and/or procedure, asignal transmitted from and/or received by a lighting system 1400 maycorrespond more closely to the occurrence of an examination and/orprocedure.

Lighting system 1400 may comprise location sensor 1401. In variousembodiments, location sensor 1401 is a transceiver which may transmitand/or receive various wireless signals, including Wi-Fi, Bluetooth,etc. In some embodiments, location sensor 1401 may be sensor 213 and/orsensor 1303. As previously described, sensor 1401 may connect to a userdevice, such as a ID tag or mobile device, including medicalprofessional mobile device 1301, which corresponds to a particularindividual, such as a medical professional (including physicians,assistants, etc.) or a patient. This connection may indicate thepresence of the corresponding individual within the examination room.

As previously described, sensor 1401 may be configured to detect an IDthat may be an active beacon or a non-powered readable tag. For example,sensor 1401 may emit an electromagnetic signal which impinges on anidentifier comprising an RFID or infrared tag to power a return signal,as previously described with reference to FIG. 2B. As another example,sensor 1401 may detect a signal emitted from the ID, such as Bluetoothor Wi-Fi signal, as previously described with reference to FIG. 2C. In afurther example, a user device may transmit a signal which can bedetected by sensor 1401 to form a connection. In various embodiments,sensor 1401 detects a signal to determine whether an individual(patient, assistant, doctor, etc.) is in or out of the exam room, aspreviously described with respect to FIGS. 2D and/or 2E.

In some embodiments, a centrally located lighting system may allow awireless signal to have a comprehensive coverage of a particular room.In other embodiments, this may allow for a wireless signal with a rangecomprising a uniform radius to be emitted without extending beyond thewalls of the room. By using a light bulb or lighting system as thesource of a sensor and/or transmitter, an omnidirectional wirelesssignal with a uniform signal range may be used to cover an exam room.For example, in a room with four walls of equal dimensions, a wirelesssignal with a signal range of equal diameter may be used to cover all ora majority of the room with minimal or not wireless signal extendingbeyond the walls of the room.

In some embodiments, lighting system 1400 may be configured to emit awireless signal with a signal range of a desired shape to correspond tothe characteristics of a given room. For example, directional wirelesstransmitters or antenna may be implemented to provide an aggregatedsignal with a signal range of a particular shape. For example, a roomwith four walls may be a rectangular configuration with two oppositewalls further from each other than the two other opposite walls. In suchan example, an omnidirectional wireless signal may be used to reach thetwo closer walls, while directional transmitters may be used to extendthe signal range to reach the two further walls. Thus, a signal that istransmitted from and/or received by lighting system 1400 may be moreclosely correlated with the presence of a particular individual withinthe room. In various embodiments, lighting system 1400 may be configuredto emit a signal to correspond to various shapes and sizes of rooms.

In some embodiments, the wireless signal transmitted by lighting system1400 may be tuned to a signal strength corresponding to the size of thecorresponding room (such as an exam room or a medical office). Invarious embodiments, the signal strength may be tuned by adjusting thegain in a signal amplifier, such as amplifier 1417. For example, a lowersignal strength may be tuned for a smaller exam room such that the rangeof the wireless signal is decreased and does not extend beyond the wallsof the exam room. As another example, a larger signal strength may betuned for a larger exam room such that the range of the wireless signalis increased to reach the walls of the exam room. In some embodiments, apredetermined localized signal range around lighting system 1400 may bedesired. For example, lighting system 1400 may be positioned at thecenter of an exam room above an examination area, and may be tuned toinclude a signal with a localized range of three feet. Thus, any userdevice may detect the wireless signal when within three feet of theexamination area.

In various embodiments, software applications may be implemented to tunethe strength. In some embodiments, such software applications may beinstalled on a computer server, such as medical scheduling managementhub 1315, which may communicate tuning instructions to lighting system1400 via notification hub interface 1411. In some embodiments, suchsoftware applications may be installed on various other devices, such asmedical professional mobile device 1301, which may communicate tuninginstructions to lighting system 1400 via medical professional deviceinterface 1421.

Thus, a centrally located wireless transmitter and/or location sensormay provide a more accurate indicator of when a particular individual iswithin the room. Through tuning and other directionality functions, awireless signal may be created that corresponds to the characteristicsof a particular room. This may also function to prevent or reduce theoccurrence false readings where part of the wireless signal rangeextends beyond the room (such as when the doctor is in the hallway nearthe room, but is recorded as being in a room). For example, if asensor/transmitter is located too close to the entrance of the examroom, part of the wireless signal range may extend beyond the exam roominto the hallway.

In particular embodiments, the location of an individual may depend uponthe strength of the connection or signal detected between sensor 1401and a user device. A stronger signal may correspond more closely to thepresence of an individual in a room because a signal detected at atransceiver in a first medical office may be several times stronger if adoctor is in the first medical office than if the doctor is in adifferent medical office. For example, location information of anindividual may not be recorded and/or detected until a user devicecorresponding to that individual detects a signal transmitted by sensor1401 that is above a predetermined threshold signal strength. In someembodiments, such signal strength may be measured in decibel-milliwatts(dBm). As another example, where the user ID is a non-powered readabletag, the user ID may not be configured to power a return signal untilthe electromagnetic signal emitted by sensor 1401 impinges on the userID above a predetermined threshold signal strength. In yet anotherexample, where the user device transmits a wireless signal, locationsensor 1401 may only record location information when the detectedsignal transmitted by the user device is above predetermined thresholdsignal strength.

Additionally, and/or alternatively, the location of an individual maydepend upon the duration of the connection or signal detected betweensensor 1401 and a user device. For example, as previously described,sensor 1401 may emit a signal as long as a user device is in range. Thelocation of an individual may be established and recorded when theduration of the connection between sensor 1401 and a user device exceedsa predetermined threshold, such as one minute for example. As alsopreviously described, sensor 1401 may emit a pulse at a regular intervalwhich forms a connection with the user device when in range. A locationof an individual may be established and recorded when a predeterminednumber of signal pulses are detected by the user device, such as 4pulses for example. In yet another example, a user device may emit apulse at a regular interval which may be detected by sensor 1401. Alocation of an individual may be established and recorded when apredetermined number of signal pulses are detected by sensor 1401. Inthese described examples, as long as a signal is detected at a regularinterval, it can be determined that the user device, and thecorresponding individual, is within range, and within the room. This maydifferentiate a more temporary connection made when an individual merelypasses by the room in the hallway.

In some embodiments, a localized signal range may be implemented foradjustable lighting systems 1400 that may be moved to desiredillumination locations in order to detect the localized presence of amedical professional and/or patient. For example, in some embodiments,the position of lighting system 1400 may be adjustable, in whichlighting system 1400 may be moved around an examination area for desiredillumination angles of the examination area and/or a patient. Becauselighting system 1400 may be adjusted by a medical professional (such asa physician or medical assistant) to illuminate a patient and/or aparticular area of the patient, in various examples, the position oflighting system 1400 may closely correspond to the location of suchpatient, medical professional and/or other individual or user. Thus, theproximity of an individual to lighting system 1400 may indicate when anexamination has begun or is in progress. In such an example, locationsensor 1401 and/or transmitter 1419 may be tuned to include a signalwith a localized range of three feet.

In further embodiments, lighting system 1400 may include transmitter1419. In some embodiments transmitter 1419 may be transmitter/receiver216, which functions both to transmit and receive signals. Suchtransmitter 1419 may be configured to transmit the location status ofthe individual to a remote processor, such as remote processor 234. Forexample, transmitter 1419 may include delay log interface 1207, whichallows data such as real-time location and time information forappointments in-progress to be transmitted to an appointment delay log1219, as previously described. Additionally, and/or alternatively,transmitter 1419 may include patient notification interface, whichnotifies upcoming patients if their appointments will be substantiallydelayed, such as at a patient mobile device 1217, as previouslydescribed.

In some embodiments, transmitter 1419 may be configured to transmitlocation status to a medical scheduling management hub 1315 vianotification hub interface 1411. As previously described with referenceto notification hub interface 1311, notification hub interface 1411 maysend data regarding real-time appointment start times to the medicalscheduling management hub 1315 for processing. In some embodiments,transmitter 1419 may be configured to transmit location status to amedical professional mobile device 1301 via a medical professionaldevice interface 1421. As previously described with reference to medicalprofessional mobile device interface 1321, medical professional mobiledevice interface 1421 is used to send messages to the medicalprofessional mobile device 1301, such as “Has the Smith 1:10 pmappointment begun?” In some embodiments, transmitter 1419 may beconfigured to transmit and receive data from patient appointment infodatabase 1335.

In certain embodiments, location sensor 1401 may transmit a wirelesssignal to a user device, such as medical professional mobile device 1301or patient device 1217 via transmitter 1419. In some embodiments,transmitter 1419 may be an integral component of location sensor 1401.For example, transmitter 1419 may function as an active beacon thattransmits a signal to one or more medical professional mobile devices,such as 1301, previously described with reference to FIG. 13. In variousembodiments, transmitter 1419 may transmit a wireless signal, such asWi-Fi, Bluetooth, etc. For example, each medical professional mobiledevice may include a location sensor that can detect the signaltransmitted by transmitter 1419. More specifically, the transmitter 1419may transmit a signal to a location sensor 1303. A signal detected bylocation sensor 1303 in the mobile device 1301, may indicate when amedical professional enters or leaves an examination room. The mobiledevice may then store such location information on a memory, such as1305, and may process such data via processor 1307. Alternatively,and/or additionally, the mobile device may transmit the locationinformation to medical scheduling management hub 1315 for processing vianotification hub interface 1311.

Various embodiments of lighting system 1400 described herein may provideadditional privacy protections within a medical setting. By constrainingthe signal range to within an examination room, lighting system 1400 maynot be accessed by devices outside of the examination room. Thus,lighting system 1400 may not be subject to unauthorized access bydevices not within the examination room, reducing the risk ofunauthorized access to sensitive medical information, such as medicalrecords 1115.

Lighting system 1400 with an integrated transceiver may provideadditional privacy protections for sensitive private medicalinformation. For example, lighting system 1400 may provide an additionalseparation between the location data and the contact information storedin non-HIPAA portions of a database, as well as the medical records 1115stored in firewalled HIPAA portions of the database, as described inFIG. 11. For example, location sensor 1401 may be used to detect aunique identification code transmitted by an ID tag corresponding to apatient and/or medical professional. Such unique identification code maybe matched with information corresponding to the patient and/or medicalprofessional stored in memory 1403 at lighting system 1400, such as byprocessor 1405. In some embodiments, such identification code may bematched to corresponding information by a secure server, such asschedule management system 1200 and/or medical scheduling management hub1315. Thus, there may be an additional separation between the locationinformation of a patient (which may correspond to when an examination isoccurring) and the patient appoint info 1101, which is further separatedfrom the patient medical records 1115.

In some embodiments, the unique identification code corresponding to aparticular individual may constantly change or cycle through a list ofidentification codes. Such code changes may be synced at lighting system1400, such as by processor 1405, so that location tracking can bematched with information corresponding to that individual. In someembodiments, such changes may be synced at a secure server, such asschedule management system 1200 and/or medical scheduling management hub1315.

In various embodiments, components in lighting element 1413 may functionas an antenna to transmit and/or receive signals, such as the radiofrequency (RF) signals (shown by the dashed line). In some embodiments,lighting element 1413 may function as an antenna for location sensor1401 and/or transmitter 1419. For example, a lighting system 1400 actingas an active beacon may transmit a signal through the wire filaments ofan incandescent lamp. In another example, the wire filaments of anincandescent lamp in lighting system 1400 may receive a signaltransmitted by an ID beacon. In other embodiments, the diode of an LEDlamp may also function to transmit and/or receive signals. For example,a high frequency signal may be applied through the DC voltage to betransmitted from the diode along with the light.

Including the sensor/transmitter and/or transceiver in lighting system1400 allows the medical scheduling management system to be incorporatedinto an essential structure of the exam room. No additional structure isrequired. This may eliminate potential clutter in an exam room in whichspace may already be designated for various tools, furniture, and otheressential appliances. Light bulbs and other lighting elements 1409 arealso easily interchangeable and are easily replaced or used in any roomwith a standardized terminal.

In the present example, lighting system 1400 may include memory 1403,which is used to store data and program instructions and maintain alocal side cache. The program instructions may control the operation ofan operating system and/or one or more applications, for example. Insome examples, the size of the memory 1403 may be limited, as when mostof the processing and storage of data is performed at the medicalprofessional mobile device 1301 and/or medical scheduling management hub1315. In addition, processor 1405 may include limited processing of thedata collected. For instance, the data collected may include the timesand locations of particular appointments and processor 1405 can be usedto format the information before sending it to the medical professionalmobile device 1301 and/or medical scheduling management hub 1315. Thelimited memory 1403 and processor 1405 sizes and capabilities may beappropriate especially in cases when lighting system 1400 is implementedas a standard lighting device for an exam room because the componentscan be smaller and more conveniently designed into a smaller casing toreduce obstruction and remain out of sight.

In various embodiments, lighting system 1400 may include display 1407.In some embodiments, display 1407 may indicate that the location sensor1401 has detected that an individual is in the exam room. For example, alight may be turned on to indicate that location sensor 1401 hasdetected the presence of a particular individual. There may be multiplelights, where each light indicates a separate individual with an ID. Thelights may be switched off when the corresponding individual leaves theexam room. In other embodiments, display 1407 may indicate variousstatus messages of lighting system 1400, including power status, errormessages, etc. In some embodiments, display 1407 may further display thetime, temperature, lighting level, etc. In some embodiments, display1407 includes user input means to allow the medical professional tointeract with the system, such as through a screen, touch screen, etc.As described above, the medical professional may input data through thisdisplay 1407 and/or view options through the display 1407.

In one or more embodiments, one or more components of lighting system1400 may be powered by the power source from the corresponding room. Forexample, a power interface 1415 may be wired into the electrical circuitof the room and/or building, which may in turn be coupled to a greaterelectrical grid. In this way, the various components of lighting system1400 depicted in FIG. 14 may have access to continuous power. In someembodiments, functioning of lighting element 1409 may be controlled by aswitch or other mechanism. However, location detection componentsdepicted in FIG. 14, (such as sensor 1401, memory 1403, processor 1405,display 1407, transmitter 1419, and/or other components) mayalternatively, and/or additionally, receiver power from a separatecircuit from lighting element 1409. For example, sensor 1401 may beelectrically coupled in parallel. This ensures that electrical power maycontinue to power the location detection functions even when the lightis turned off, which may occur for various examination purposes. Forexample, the assistant or physician may still be in the exam room whenthe light is turned off, but it may be determined that the physician hasleft the exam room if the location detection components were also turnedoff. In some embodiments, function of lighting element 1409 may becontrolled by a separate switch mechanism from the function of variousother components of lighting system 1400. Thus, power may becontinuously supplied to the components of lighting system 1400, but thecircuit for lighting element 1409 may be open and closed via a separateswitch mechanism.

In some embodiments, a separate power supply 1413 is included to powerone or more components of lighting system 1400. In some embodiments,power supply 1413 is electrically coupled to power interface 1415. Insome embodiments, the power supply 1413 may comprise a separate batteryincluded in the lighting system 1400 to power the location detectioncomponents. In yet further embodiments, the battery may be arechargeable battery that is charged by the electrical power source ofthe exam room. For example, power supply 1413 may be charged by thepower source of the room when a switch is activated to power lightingelement 1409. In some embodiments, the power supply 1413 comprises acapacitor which may store a charge from the electrical power source.Such capacitor may build up and store a charge when the exam room'spower is turned on. In some embodiments, the capacitor may store enoughcharge to power the location detection components for a predeterminedamount of time, such as 12 hours. Complete power loss of the locationdetection components after 12 hours may be acceptable as it is likelythat nobody is in the exam room if the lights have been off for 12 ormore hours. In various embodiments the capacitor may store any amount ofcharge appropriate for the operation of lighting system 1400.

As previously described, using lighting structures as a sensor locationmay be advantageous because lighting structures are generally located atthe center of an examination room, which may enable a transmittedwireless signal to maintain a general coverage of the examination roomwithout extending beyond the walls of the examination room. Furthermore,lighting structures are generally centered about the patient. Forexample, lighting system 1400 may be adjusted by the physician to adesired location around a patient for a particular examination and/oroperation procedure. Thus, the position of a medical professional and/orpatient relative to lighting system 1400 may be closely correlated tothe occurrence of an examination. According to various embodiments,medical personnel and/or patients are not required to login, check in,or do any extra work to indicate their presence in a room. Instead,their location is tracked based on the signals received at the variousBluetooth or Wi-Fi transceivers within lighting system 1400 toautomatically manage scheduling. Furthermore, lighting system 1400 mayprovide added privacy protection for sensitive medical informationprotected by HIPAA.

Various other lighting systems that may be implemented with variousembodiments of the present disclosure are further described in U.S.patent application Ser. No. 15/439,787 by Bullington et al., filed onFeb. 22, 2017, titled LIGHTING SYSTEM FOR MEDICAL APPOINTMENT PROGRESSTRACKING, which is incorporated by reference herein in its entirety andfor all purposes.

In some embodiments, location sensor 1401 in lighting system 1400 maycomprise a Wi-Fi extender, which may alternatively be referred to hereinas a WiFi booster or repeater. The Wi-Fi extender of sensor 1401 may beconfigured to connect to an existing wireless network and retransmit thesignal corresponding to the size and other characteristics of a room, aspreviously described. For example, a medical-office may include abroadcast and multicast and/or unicast wireless network.

FIG. 15 illustrates an example network architecture 1500 that can beused in conjunction with the various techniques and embodiments of thepresent disclosure. In various embodiments, network architecture 1500may be a broadcast and multicast/unicast system. The networkarchitecture 1500 includes a number of user devices 1502 and 1504communicably connected to server system 1512 by a network 1510.

In various embodiments, network 1510 may be a wired and/or wirelessnetwork. In some embodiments, network 1510 may be a local area network(LAN), which interconnects computers and devices within a limited area.In other embodiments, network 1510 may comprise other network types,such as a wide area network (WAN), or a global network, such as theInternet. In some embodiments, network 1510 may be an unsecured wirelessnetwork. However, in other embodiments, network 1510 may be a securewireless network in which various devices and systems may requireauthorization to access network 1510. Various security protocols may beimplemented to prevent unauthorized access to sensitive private medicalinformation protected under HIPAA. Such secure network may implementvarious network protection protocols, including WEP, WPA, and WPA2.

In some embodiments, mobile device 1502 and/or 1504 may be a user ID,such as ID 211, ID, 221, or ID 231, as described with reference to FIG.2A, and/or a medical professional mobile device 1301, as described withreference to FIG. 13. In some embodiments, mobile device 1502 includesmultiple receivers for receiving both broadcast and multicast/unicastdata, such as data from IP networks delivered over cellular, mobile,WiFi, etc. Although only two user devices are depicted in FIG. 15, itshould be recognized that architecture 1500 may include any number ofuser devices corresponding to individuals, such as medical professionalsand/or patients.

In some embodiments, server system 1512 may be schedule managementsystem 1200 and/or medical scheduling management hub 1315. In someembodiments, server system 1512 includes one or more processors andmemory. The processors of server system 1512 execute computerinstructions (e.g., network computer program code) stored in the memoryto perform functions of a network data exchange server.

As previously described, server system 1512 may function as a contentserver configured to receive and store network profile information,including appointment change status info 1141, patient appointment info1101, and/or patient medical records 1115. Server system 1512 may alsofunction as a dispatch server configured to transmit and/or routenetwork data packets including network messages. In some embodiments,the network architecture 1500 may further include a database 1514communicably connected to user devices 1502 and 1504, and server system1512 via network 1510. In some embodiments, database 1514 may bedatabase 1100. In some embodiments, network data, or other informationsuch as appointment information and patient information may be stored inand/or retrieved from database 1514. In some embodiments, database 1514is a component within server system 1512 and stored within memory ofserver system 1512. Although only one server system is depicted in FIG.15, it should be recognized that architecture 1500 may include anynumber of server systems configured to perform one or more of thefunctionalities described above.

In various embodiments, network architecture 1500 includes a signalsource device 1516. Source device 1516 may connect network 1510 with aglobal network such as the Internet. In some embodiments, source device1516 may be a modem and/or router. In some embodiments source device1516 may be a wireless router. In some embodiments, source device 1516may wirelessly connect server system 1512 to network 1510. In someembodiments, source device 1516 may be a component within server system1512.

In various embodiments, network architecture includes wireless accesspoint (WAP) 1518. In some embodiments, one or more WAPs 1518 may beconnected to a wired network and provide wireless access to the LAN. Insome embodiments, user devices 1502 and 1504 may connect to network 1510via wireless access point (WAP) 1518. WAP 1518 may be a networkinghardware device that allows a Wi-Fi compliant device, such as userdevices 1502 and 1504, to connect to network 1510. In some embodiments,WAP 1518 may connect to network 1510 via source device 1516, such as arouter (via a wired or wireless network), as a standalone device.However, in some embodiments, WAP 1518 may be an integral component ofsource device 1516. In some embodiments WAP 1518 may be wirelesslyconnected to network 1510.

Users of the client devices 1502 and 1504 may access the server system1512 to participate in a network data exchange service, such as amedical appointment scheduling service. For example, the client devices1502 and 1504 can execute web browser applications that can be used toaccess the network data exchange service. In another example, the clientdevices 1502 and 1504 can execute software applications that arespecific to the network (e.g., networking data exchange “apps” runningon smartphones). In further embodiments, client devices 1502 and 1504are configured to use global position system (GPS), or othergeo-location capabilities, to determine a user's location.

Users interacting with the user devices 1502 and 1504 can participate inthe network data exchange service provided by the server system 1512 byproviding appointment requests and other patient related data. In someimplementations, the client devices 1502 and 1504 can be computingdevices such as laptop or desktop computers, smartphones, personaldigital assistants, portable media players, tablet computers, or otherappropriate computing devices that can be used to communicate with anetwork. In some implementations, the server system 1512 can include oneor more computing devices such as a computer server. In someimplementations, the server system 1512 can represent more than onecomputing device working together to perform the actions of a servercomputer (e.g., cloud computing). In some implementations, the network1510 can be a public communication network (e.g., the Internet, cellulardata network, dial up modems over a telephone network) or a privatecommunications network (e.g., private LAN, leased lines).

In some embodiments the Wi-Fi extender of sensor 1401 may comprise twoor more wireless routers. A first wireless router may be configured toconnect to a wireless signal of an existing network, such as network1510. The first wireless router may receive the wireless signal viasource device 1516. For example, a Wi-Fi signal may be transmitted bysource device 1516, such as a server, a mobile device, router, oranother wireless access point on the wireless network. For example,transmitter/receiver 236, as depicted in FIG. 2A, may be a source device1516 which transmits a wireless signal. As another example, schedulemanagement system 1200 may include a source device 1516 which transmitsa wireless signal.

The first wireless router may then transfer the wireless signal to asecond wireless router in the Wi-Fi extender, which rebroadcasts thatWi-Fi signal into the room. In some embodiments, the Wi-Fi extender mayfunction as a wireless access point 1518 to connect to user devices thatare in range within the room. User devices, such as user IDs or medicalprofessional mobile devices, may then connect to the network via thesignal rebroadcasted by the Wi-Fi extender.

In some embodiments, the Wi-Fi extender may be a single band repeater,which receives, then retransmits each packet of data using the sameradio on the same channel. However, in some embodiments, the Wi-Fiextender may be a dual band repeater, which may communicate with sourcedevice 1516 and rebroadcast on different channels. For example, theWi-Fi extender may receive a wireless signal from a main router on lowerchannels and then rebroadcast the wireless signal on higher channels. Aspreviously described, the wireless signal may be tuned to a strengthand/or shape corresponding to the characteristics of the room.

In some embodiments, the Wi-Fi extender may be directly connected anetwork via a wired connection, such as via Ethernet. In someembodiments, the Wi-Fi extender of sensor 1401 may comprise a powerlineadapter, such as a powerline Ethernet adapter, which is configured toreceive a network signal sent from a router or other source device 1516over electrical circuits. For example, a first adapter may be connectedto a source device 1516, such as a router, via a direct wiredconnection, such as Ethernet. The first adapter may then be plugged intoa power outlet coupled to an electrical circuit. The first adapter maybe configured to transmit the network signal from the source device 1516through the electrical circuit to a second powerline Ethernet adapterwithin location sensor 1401 of lighting system 1400, which is pluggedinto another power outlet coupled to the electrical circuit. The secondadapter of location sensor 1401 may be configured to convert the signalto a wireless signal within the room to connect with user devices. Aspreviously described, the wireless signal may be tuned to a strengthand/or shape corresponding to the characteristics of the room.

As such, the network signal may travel with the same electrical currentthat powers lighting system 1400 along an electrical circuit from thepower source to lighting system 1400. In some embodiments, theelectrical current including the network signal may run directly frompower supply 1413 to power interface 1415, which supplies the electricalcurrent to lighting interface 1408. In some embodiments, the electricalcurrent is used to power lighting element 1409 to emit light. Ascompared to a Wi-Fi extender comprising a plurality of wireless router,by transmitting the network signal through the electrical current viapowerline adapters may add an additional level of security for thenetwork. Because there the network signal is not transmitted to the roomvia wired connection, there is one less step of signal transmission thatis done wirelessly. Therefore, the transmission of the signal to theWi-Fi extender is direct and not subject to possible reception by otherunauthorized devices. Furthermore, a direct transmission of a networksignal via electrical current is more direct and immediate with lessdrop off in signal strength.

As previously described, lighting element 1409 may additionally functionas an antenna to emit the network signal from the electrical current asa wireless signal. However, in some embodiments, lighting system 1400may include a separate transmitter, such as transmitter 1419, configuredto emit the network signal as a wireless signal. In some embodiments,lighting element 1409 may function as a broadcast and/or receiverantenna for transmitter 1419. Wireless signals, including data packets,received by lighting system 1400 may similarly be transmitted throughthe electrical circuit to the source device 1516 and/or to a serversystem. In this way, the same electrical current directed to lightingsystem 1400 may provide power to the lighting element 1409 and variousother components of lighting system 1400, as well as the network signal.As such, the various components of lighting system 1400 depicted in FIG.14 may have access to the network signal, which also provides continuouspower.

In various implementations, the Wi-Fi extender of location sensor 1401in a room may transmit information identifying the room such that a userdevice may identify the room location corresponding to the receivedsignal. In some embodiments, each Wi-Fi extender the lighting system1400 of a room includes a unique IP address and/or MAC address. Suchinformation may be included within data packets transmitted through thewireless signal by the Wi-Fi extender.

According to various embodiments, data may be transmitted by the Wi-Fiextender over the wireless network that implements standards from theIEEE 802.11 standards family, such as Wi-Fi. Such data may betransmitted in the form of data packets corresponding to a seven-layerOpen Systems Interconnection (OSI) model of computer networking andutilize standard protocols such as transmission control protocol (TCP)or user datagram protocol (UDP). A typical UDP data packet correspondingto an IEEE 802.11 wireless standard includes a media access control(MAC) sublayer of the data-link layer, organized as a MAC frameconsisting of a MAC header, a frame body, and a frame check sequence(FCS) as further explained below in FIG. 16.

As previously explained, in some implementations, the wireless networkis a secure wireless network. The data within the frame body of a datapacket sent over a secure wireless network, called a payload, isencrypted and cannot be read by a user device that is not authorized toreceive data packets on the secure wireless network. However, in someimplementations, data packets may be sent via multicast format, such asIP multicast, application layer multicast, or multicast over otherwireless networks. An example of an IP multicast technique may utilizeone or more IP multicast group addresses as destination IP addressesthat are stored in the MAC headers of the sent data packets. Suchmulticast data packets may be sent by the Wi-Fi extender via a wirelesscommunication interface, such as transmitter 1419. In some embodiments,the destination IP addresses include MAC addresses reserved specificallyfor Ethernet multicast.

In other embodiments, the Wi-Fi extender may send a simple servicediscovery protocol (SSDP) to continuously scan for the presence of userdevices. In some embodiments, the Wi-Fi extender may transmit multi-castdata packets 1620 when a user device has been detected. In otherembodiments, the Wi-Fi extender may continuously transmit multicast datapackets with information corresponding to the identification of theroom. In some implementations, a user device may include hardware, suchas a wireless interface, configured to scan for and receive multiplemulticast data packets addressed to one or more IP multicast groupaddresses over a wireless network. In some embodiments, the user devicemay be set to an initial listening mode to actively search for wirelesscommunications being sent on various communication channels. Forexample, 2.4 GHz Wi-Fi has 14 channels for communication, 11 of whichare approved for use. When in listening mode, the user device spends acertain amount of time, such as 1 second, on each channel to detect fortransmission. Once a transmission is detected on a particular channel,the user device may stay tuned to the particular channel to receive thesent multicast data packets.

In some embodiments, a user device may not have access to the securewireless network when receiving the multicast data packets. For example,the Wi-Fi extender of lighting sensor 1400 may provide the same networkprotection as existing routers, such as WEP, WPA and WPA2. In otherembodiments, the wireless connection device may not be authorized toaccess the secure wireless network and thus, cannot decrypt encryptedportions of the multicast data packets. By restricting access to thesecure wireless network by a user device, the system may provide foradditional network security, such as for HIPAA related information. Insome embodiments, only user devices corresponding to certain individualsmay be restricted. For example, user devices corresponding to patientsmay not have access to the secure network. However, in some embodiments,user devices corresponding to medical professionals may have access tothe secure network.

Although a user device may not have access to the secure wirelessnetwork, the unauthorized wireless connection device may still receiveand read the MAC addresses of multicast data packets sent over a securewireless network. In some embodiments, the Wi-Fi extender may send outmultiple multicast data packets to one or more specific destination IPaddresses such that a source IP address associated with the Wi-Fiextender is mapped to one or more MAC addresses in the MAC frame of adata packet.

With reference to FIG. 16, shown is an illustration of an embodiment ofa typical IEEE 802.11 MAC frame 1600 for a multicast data packet, inaccordance with one or more embodiments. Such multicast data packet maybe transmitted by a wireless access point 1518, such as a Wi-Fi extenderof location sensor 1401. MAC frame 1600 includes the following fields:frame control 1602, duration/ID 1604, sequence control 1612, frame body1616, frame check sequence 1618, and MAC addresses 1606, 1608, 1610, and1614. Frame body 1616 contains data and/or information organized as IPpacket 1620. IP packet 1620 includes IP header 1622 and variable-lengthdata field 1624. IP header 1622 consists of several fields includingversion 1626, internet header length (IHL) 1628, type of service (ToS)1630, total length 1632, identification 1634, flags 1636, fragmentoffset 1638, time to live (TTL) 1640, protocol 1642, checksum 1644,source IP address 1646, destination IP address 1648, and options 1650.The data and/or information in data field 1624, also known as the“payload,” is encrypted. In certain embodiments, the data and/orinformation in data field 1624 may be unencrypted. In certainembodiments, IP packet 1620 may not include one or more of the fieldsshown in FIG. 16, or may include one or more additional fields.

In some embodiments, source IP address 1646 may be a standard 162-bitaddress utilized in Internet Protocol version 4 (IPv4), and an addressdesignated as Class D, which are reserved for multicast services. Thelower 23 bits of source IP address 1646 may be directly mapped to MACaddress 1606 in a hexadecimal base 16 format. In other embodiments, thesource IP address 1646 may be directly mapped to any of the other MACaddresses in the MAC header, including 1608, 1610, and/or 1614. In someembodiments, a user device may receive multiple multicast packets whenin range of the Wi-Fi extender of location sensor 1401 and identify thevalue of MAC address field 1606 of each packet to determine thecorresponding room. In some embodiments, the user device may directlyread the source IP address 1646.

According to various embodiments, the wireless connection device mayinclude memory and a processor that is configured to identify the sourceIP address 1646 mapped to MAC address 1606 corresponding to the Wi-Fiextender in a particular room. In some embodiments, the locationinformation may be sent to a server system, such as schedule managementsystem 1200 or medical scheduling management hub 1315, for additionalprocessing to identify the location of the individual corresponding tothe user device, as well as to determine appointment scheduling changes.In some embodiments, the location information may also include durationof the wireless connection. In some embodiments, some of the processingof the location data may be performed at the user device. For example,the user device may identify the location of the individualcorresponding to the user device and the start time and end time of theconnection. In some embodiments, the user device may then record thelocation information

In some embodiments, a user device may have access to the network. Inother embodiments, the network may not be a secure network. In suchinstances, information corresponding to the identity of the room may betransmitted within the data field 1624 of the multicast IP packet 1620,which may be read by the user device.

In other embodiments, a user device may be configured to transmit datapackets 1620 to lighting system 1400 when connected to the wirelesssignal broadcasted by the Wi-Fi extender. In some embodiments, the userdevice may continue to transmit data packets 1620 when in range of thewireless signal transmitted by the Wi-Fi extender. In other embodiments,the user device may send a simple service discovery protocol (SSDP) tocontinuously scan for the presence of Wi-Fi extenders and/or otherwireless access points 1518. In some embodiments, the user device maytransmit multi-cast data packets 1620 when a Wi-Fi extender of alighting system has been detected. In other embodiments, the user devicemay continuously transmit multicast data packets with informationcorresponding to the identification of the user device and/orcorresponding individual.

Such data packets may include source IP address information 1646 and/orMAC address information 1648 corresponding to that user device. Suchdata packets 1620 may be received at lighting system 1400 at a wirelessinterface, such as by medical professional mobile device interface 1421.In some embodiments, processor 1405 of lighting system 1400 may beconfigured to determine the identity of the individual correspondingbased upon the source IP address 1646 and/or MAC address information1648. In some embodiments processor 1405 may further record the durationof the connection. In some embodiments, the location information istransmitted to a server system, such as schedule management system 1200and/or medical scheduling management hub 1315, by lighting system 1400via an interface, such as notification hub interface 1411, forprocessing to determine appointment scheduling changes. However, in someembodiments, the data packets 1620 received from a user device may besent directly to a server system for processing to determine theidentity and location of the individual corresponding to the userdevice, as well as to determine appointment scheduling changes.

With reference to FIGS. 17A-17C, shown is an example method 1700 forappointment progress tracking, in accordance with one or moreembodiments. In various embodiments, method 1700 may be a method formedical appointment progress tracking for improving patient wait timesfor medical appointments, as previously described in the presentapplication. At operation 1701, a power interface of a lighting system1721 is coupled to a power source. In some embodiments, a power sourcemay be an electrical circuit, such as electrical circuit 1737, which isfurther described below.

In some embodiments, the lighting system 1721 may be lighting system1400. In some embodiments, the lighting system 1721 comprises a lightingfixture 1723 in a medical examination room. As previously described, thelighting fixture 1723 may be centrally located in the medicalexamination room. In some embodiments, the lighting fixture 1723 may bemounted on the ceiling at the center of the examination room. In otherembodiments, the lighting fixture 1723 may be adjustable such that theposition of lighting system 1723 may be moved around a patient and/or anexamination area for illumination of desired areas of the patient and/orexamination area.

In some embodiments, the lighting fixture 1723 includes a lightinginterface configured to connect to a lighting element 1725 forilluminating the medical examination room. In various embodiments,lighting element 1725 may be lighting element 1413. As previouslydescribed, lighting interfaces may comprise a base with terminals fortransferring electrical power to a lighting element 1725 comprising awire filament. In other embodiments, a lighting interface may compriseanode and cathode leads to provide electrical current to a lightingelement 1725 comprising one or more LEDs. In yet further embodiments,where a lighting element 1725 comprises a light bulb, a lightinginterface may comprise one or more various light bulb couplings, such asa standard Edison screw coupling.

In some embodiments, the lighting fixture 1723 also includes a Wi-Fitransceiver 1727 configured to receive a network signal of a local areanetwork. In various embodiments, Wi-Fi transceiver 1727 may be alocation sensor, such as location sensor 1401, which comprises a Wi-Fiextender. Other signal transceivers may be implemented in variousembodiments, such as Bluetooth or infrared signals.

In various embodiments, Wi-Fi transceiver 1727 may be configured toconnect to an existing network signal and wirelessly transmit thenetwork signal into the examination room. As such, a wireless signal1741 is transmitted, via the Wi-Fi transceiver 1727, to connect to adevice corresponding to a physician at 1703. The wireless signal 1741may correspond to the network signal of the local area network. In someembodiments, the device may be a user device, such as an ID tag (e.g.,ID tags 211, 221, and 231) and/or a medical professional mobile device1301.

In some embodiments, the Wi-Fi transceiver 1727 may connect to theexisting network signal of the local area network wirelessly. Forexample, in certain implementations, the Wi-Fi transceiver 1727comprises a plurality of wireless routers 1729. A first router 1731 maybe configured to receive a wireless network signal corresponding to thenetwork signal of the local area network. A second router 1733 may beconfigured to rebroadcast the wireless network signal as the wirelesssignal 1741.

In some embodiments, the Wi-Fi transceiver 1727 may connect to theexisting network signal of the local area network through a wiredconnection. For example, the Wi-Fi transceiver 1727 may be connected toa network source, such as a router or modem, via Ethernet cable. Asanother example, in other implementations, the Wi-Fi transceiver 1727comprises a powerline adapter 1735 coupled to the power source via anelectrical circuit 1737. The powerline adapter 1735 may be configured toreceive the network signal of the local area network over the electricalcircuit 1737 and transmit the network signal as the wireless signal1741. The Wi-Fi transceiver 1735 and the lighting element 1725 may beelectrically coupled (1739) in parallel.

At 1705, the signal strength of the wireless signal 1741 is tuned tocorrespond to the size and characteristics of the medical examinationroom, such as via amplifier 1417. As previously described, a thetransmission power of Wi-Fi transceiver 1727 may be decreased for asmaller examination room, such that the signal range of the transmittedwireless signal 1741 is shortened and does not extend beyond the wallsof the examination room. Alternatively, the transmission power of Wi-Fitransceiver 1727 may be increased for a larger examination room, suchthat the signal range of the transmitted wireless signal 1741 isextended up to, but not beyond the walls of the examination room. Invarious embodiments, unidirectional antennas may be implemented tocreate a signal range of a desired shape to correspond to thecharacteristics of a given room.

At 1707, a plurality of multicast data packets 1743 are transmitted viathe Wi-Fi transceiver 1727 to the device during the duration of theconnection. Each multicast data packet 1743 may include informationidentifying the medical examination room. As previously described, thepayload of each data packet 1743 may include information identifying thecorresponding examination room, in which the Wi-Fi transceiver 1727 islocated in. Such information may be received and identified by a userdevice with access to the local area network, which may be a securenetwork.

As also previously described, each Wi-Fi transceiver 1727 may have aunique IP address. Each unique IP address may be associated with thecorresponding examination room in which the Wi-Fi transceiver 1727 islocated in. The IP address may be located in the source IP address field1646 and/or one or more MAC address fields, such as MAC address 1606. Auser device that receives multicast data packets 1743 may process andidentify the examination room based on the source IP address and/or MACaddress even if it does not have access to a secure network.

In some embodiments, data packets 1743 including such information mayadditionally, and/or alternatively, be sent to a server system such asschedule management system 1200 or medical scheduling management hub1315 for identification of the examination room.

At 1709, a plurality of multicast data packets 1745 are received fromthe device during the duration of the connection. Each multicast datapacket 1745 may include information identifying the correspondingphysician. In some embodiments, such information may identify anotherindividual corresponding to the device, such as a medical professionalor patient. Each user device that transmits data packets over Wi-Fi mayinclude a unique IP address. As in step 1707, the unique IP address maybe located in the source IP address field 1646 and/or one or more MACaddress fields of multicast data packets 1745 transmitted by a userdevice. Lighting system 1721 may receive such information to identifythe device, and the corresponding individual (such as a physician,medical professional, or patient), that has formed a connection.Information identifying the corresponding individual may additionally,and/or alternatively, be included in the payload of a data packet 1745.

In some embodiments, data packets 1745 including such information mayadditionally, and/or alternatively, be sent to a server system such asschedule management system 1200 or medical scheduling management hub1315 for identification of the corresponding individual.

At 1711, the presence of the physician in the medical examination roomis tracked based on the duration of the connection, such as previouslydescribed in FIGS. 4A-4C and FIG. 6. For example, a timestamp may belogged based on the duration of the connection indicating the durationof a first appointment, at 1713. As previously described a processor maybe configured to record when the connection is first made between theWi-Fi transceiver 1727 and the device. The processor may be processor1405 in lighting system 1400. In other embodiments, the processor may beprocessor 1205 and/or 1307. In various embodiments, the connection maybe recorded by a timestamp. A timestamp may be logged at the time aconnection is made between the Wi-Fi transceiver 1727 and the device. Insome embodiments, the time a connection is made may be determined basedon when the Wi-Fi transceiver 1727 begins receiving data packets 1745transmitted from the device, and/or when the device begins receivingdata packets 1743 transmitted from the Wi-Fi transceiver 1727. Atimestamp may also be logged at the time the connection between theWi-Fi transceiver 1727 and the device is terminated. In someembodiments, the time a connection is terminated may be determined basedon when the Wi-Fi transceiver 1727 stops receiving data packets 1745transmitted from the device, and/or when the device stops receiving datapackets 1743 transmitted from the Wi-Fi transceiver 1727.

At 1715, the timestamp is compared with scheduling information 1747 topredict whether future appointments will be substantially delayed, suchas in step 611 previously described with reference to FIG. 6. In someembodiments, scheduling information 1747 includes a plurality ofscheduled appointments, which include the first appointment and a secondappointment. At 1717, a holder of the second appointment is notified ifthe second appointment is determined to be substantially delayed, suchas in step 623.

Various computing devices can implement the methods and systemsdescribed. For instance, a mobile device, computer system, etc. can beused to generate artificially rendered images. With reference to FIG. 18shown is a particular example of a computer system that can be used toimplement particular examples of the present disclosure. According toparticular example embodiments, a system 1800 suitable for implementingparticular embodiments of the present disclosure includes a processor1801, a memory 1803, an interface 1811, and a bus 1815 (e.g., a PCI busor other interconnection fabric) and operates as a streaming server. Theinterface 1811 may include separate input and output interfaces, or maybe a unified interface supporting both operations.

In some embodiments, processor 1801 may be processors 1205, 1307, 1317,and/or 1405. When acting under the control of appropriate software orfirmware, the processor 1801 is responsible for processing, modifying,transmitting, and/or receiving data packets, such as data packets 1743and/or 1745, to a user device, such IDs 211, 221, and 231, and/ormedical professional mobile device 1301, such as in steps 1707 and 1709.In other embodiments, processor 1801 is responsible for receiving datapackets sent by a user device and/or lighting system, as well as readingthe MAC addresses and/or other portions of such data packets asdescribed in FIG. 16. Various specially configured devices can also beused in place of a processor 1801 or in addition to processor 1801. Thecomplete implementation can also be done in custom hardware.

The interface 1811 is typically configured to send and receive datapackets or data segments over a network. Particular examples ofinterfaces the device supports include Ethernet interfaces, frame relayinterfaces, cable interfaces, DSL interfaces, token ring interfaces, andthe like. In some embodiments, interface 1811 may be location sensor1401 and/or transmitter 1419. In some embodiments, interface 1811 may beinterfaces 1207, 1211, and/or 1213 in schedule management system 1200.In some embodiments, interface 1811 may be interfaces 1311, 1321, and/or1325 in medical appointment delay notification system 1300.

In addition, various very high-speed interfaces may be provided such asfast Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces,HSSI interfaces, POS interfaces, FDDI interfaces and the like.Generally, these interfaces may include ports appropriate forcommunication with the appropriate media. In some cases, they may alsoinclude an independent processor and, in some instances, volatile RAM.The independent processors may control such communications intensivetasks as packet switching, media control and management.

According to particular example embodiments, the system 1800 uses memory1803 to store data and program instructions and maintained a local sidecache. The program instructions may control the operation of anoperating system and/or one or more applications, for example. Thememory or memories may also be configured to store received metadata andbatch requested metadata. In some embodiments, memory 1803 may be memory1203, 1305, 1319, and/or 1403.

According to various embodiments, the system 1800 is a server that alsoincludes a transceiver, streaming buffers, and memory. The server mayalso be associated with configuration management, logging and reportgeneration, and monitoring capabilities. Particular embodiments,functionality for allowing operation with mobile devices such ascellular phones operating in a particular cellular network and providingsubscription management. According to various embodiments, anauthentication module verifies the identity of devices including mobiledevices. A logging and report generation module tracks mobile devicerequests and associated responses. A monitor system allows anadministrator to view usage patterns and system availability. Accordingto various embodiments, the fragment server handles requests andresponses for media content related transactions while a separatestreaming server provides the actual media streams.

Because such information and program instructions may be employed toimplement the systems/methods described herein, the present disclosurerelates to tangible, machine readable media that include programinstructions, state information, etc. for performing various operationsdescribed herein. Examples of machine-readable media include hard disks,floppy disks, magnetic tape, optical media such as CD-ROM disks andDVDs; magneto-optical media such as optical disks, and hardware devicesthat are specially configured to store and perform program instructions,such as read-only memory devices (ROM) and programmable read-only memorydevices (PROMs). Examples of program instructions include both machinecode, such as produced by a compiler, and files containing higher levelcode that may be executed by the computer using an interpreter.

While the present disclosure has been particularly shown and describedwith reference to specific embodiments thereof, it will be understood bythose skilled in the art that changes in the form and details of thedisclosed embodiments may be made without departing from the spirit orscope of the disclosure. It is therefore intended that the disclosure beinterpreted to include all variations and equivalents that fall withinthe true spirit and scope of the present disclosure. Although many ofthe components and processes are described above in the singular forconvenience, it will be appreciated by one of skill in the art thatmultiple components and repeated processes can also be used to practicethe techniques of the present disclosure.

What is claimed is:
 1. An apparatus comprising: a lighting interfaceconfigured to connect to a lighting element for illuminating a medicalroom; a power interface coupled to a power source; and a wirelesstransceiver configured to transmit a wireless signal to connect to adevice for a duration, wherein the device corresponds to a user, andwherein the wireless signal corresponds to a local area network; whereina length of the duration of the connection is used to track a presenceof the user in the medical room; and wherein the apparatus is located ina lighting fixture in the medical room.
 2. The apparatus of claim 1,wherein the lighting fixture is centrally located in the medical room.3. The apparatus of claim 1, wherein the wireless transceiver isconfigured to transmit a plurality of multicast data packets to thedevice during the duration of the connection, each multicast data packetincluding information identifying the medical room.
 4. The apparatus ofclaim 1, wherein the wireless transceiver is configured to receive aplurality of multicast data packets from the device during the durationof the connection, each multicast data packet including informationidentifying the user.
 5. The apparatus of claim 1, wherein the apparatusis configured to log a timestamp based on the duration of the connectionindicating the duration of a first appointment.
 6. The apparatus ofclaim 5, wherein the apparatus is further configured to compare thetimestamp with scheduling information to predict whether futureappointments will be substantially delayed, wherein schedulinginformation includes a plurality of scheduled appointments, theplurality of scheduled appointments including the first appointment anda second appointment.
 7. The apparatus of claim 6, wherein the apparatusis further configured to notify a holder of the second appointment ifthe second appointment is determined to be substantially delayed.
 8. Theapparatus of claim 1, wherein the wireless transceiver comprises aplurality of wireless routers, wherein a first router is configured toreceive a wireless network signal corresponding to a network signal ofthe local area network, and wherein a second router is configured torebroadcast the wireless network signal as the wireless signal.
 9. Theapparatus of claim 1, wherein the wireless transceiver comprises apowerline adapter coupled to the power source via an electrical circuit,wherein the powerline adapter is configured to receive a network signalof the local area network over the electrical circuit and transmit thenetwork signal as the wireless signal; wherein the wireless transceiverand the lighting element are electrically coupled in parallel.
 10. Asystem comprising: a lighting fixture in a medical room; and a locationtracking apparatus located in the lighting fixture, the locationtracking apparatus comprising: a lighting interface configured toconnect to a lighting element for illuminating a medical room; a powerinterface coupled to a power source; and a wireless transceiverconfigured to transmit a wireless signal to connect to a device for aduration, wherein the device corresponds to a user, and wherein thewireless signal corresponds to a local area network; wherein a length ofthe duration of the connection is used to track a presence of the userin the medical room.
 11. The system of claim 10, wherein the lightingfixture is centrally located in the medical room.
 12. The system ofclaim 10, wherein the wireless transceiver is configured to transmit aplurality of multicast data packets to the device during the duration ofthe connection, each multicast data packet including informationidentifying the medical room.
 13. The system of claim 10, wherein thewireless transceiver is configured to receive a plurality of multicastdata packets from the device during the duration of the connection, eachmulticast data packet including information identifying the user. 14.The system of claim 10, wherein the apparatus is configured to log atimestamp based on the duration of the connection indicating theduration of a first appointment.
 15. The system of claim 14, wherein thesystem is further configured to compare the timestamp with schedulinginformation to predict whether future appointments will be substantiallydelayed, wherein scheduling information includes a plurality ofscheduled appointments, the plurality of scheduled appointmentsincluding the first appointment and a second appointment.
 16. The systemof claim 10, wherein the wireless transceiver comprises a plurality ofwireless routers, wherein a first router is configured to receive awireless network signal corresponding to a network signal of the localarea network, and wherein a second router is configured to rebroadcastthe wireless network signal as the wireless signal.
 17. The system ofclaim 10, wherein the wireless transceiver comprises a powerline adaptercoupled to the power source via an electrical circuit, wherein thepowerline adapter os configured to receive a network signal of the localarea network over the electrical circuit and transmit the network signalas the wireless signal; wherein the wireless transceiver and thelighting element are electrically coupled in parallel.
 18. A method forappointment progress tracking, the method comprising: coupling a powerinterface of a lighting system to a power source, wherein the lightingsystem comprises: a lighting fixture in a medical room, the lightingfixture including: a lighting interface configured to connect to alighting element for illuminating the medical room, and a wirelesstransceiver configured to receive a network signal of a local areanetwork; transmitting, via the wireless transceiver, a wireless signalto connect to a device for a duration, wherein the device corresponds toa user, and wherein the wireless signal corresponds to the networksignal; and tracking a presence of the user in the medical room based ona length of the duration of the connection.
 19. The method of claim 18,further comprising transmitting, via the wireless transceiver, aplurality of multicast data packets to the device during the duration ofthe connection, each multicast data packet including informationidentifying the medical room.
 20. The method of claim 18, furthercomprising receiving a plurality of multicast data packets from thedevice during the duration of the connection, each multicast data packetincluding information identifying the user.